Safeguard
Vulnerability Analysis•

CVE-2021-35002: High File Upload Code Execution in BMC Track-It!

CVE-2021-35002 is an authenticated file upload to code execution flaw in BMC Track-It! 20.19.01 to 20.19.03. Apply the BMC update and trim service rights.

Safeguard Security Team
3 min read

CVE-2021-35002 is a high severity (CVSS 8.8) unrestricted file upload in BMC Track-It! that leads to remote code execution in the context of the service account. It affects 20.19.01, 20.19.02 and 20.19.03 and needs a login. BMC issued an update, so check the BMC article for the fixed build.

What's affected

  • BMC Track-It! 20.19.01, 20.19.02 and 20.19.03, per the NVD record.
  • The flaw is in the processing of email attachments, according to the Zero Day Initiative advisory ZDI-22-002.
  • ZDI says BMC has issued an update to correct the vulnerability. We could not retrieve the BMC article, so check it for the exact fixed version.
  • ZDI timeline: reported to the vendor on 30 July 2021 and coordinated public release on 6 January 2022.
  • Authentication is required. KEV status: false.

How to check if you're exposed

In Track-It!, check the installed build number in the application or installer details and compare it with the three affected builds. Then review the server for the account that runs the service, since code would run in that context.

Also check the folders where attachments land for unexpected file types.

What to do now

  1. Read the BMC article on Track-It! security fixes and install the update for your version.
  2. Run the Track-It! service as an account with the minimum rights it needs, not as a domain administrator.
  3. Restrict the mailbox or intake paths that feed attachments into Track-It! to expected senders where possible.
  4. Block script and executable file types from attachment storage locations.
  5. Review recent attachment activity and server logs for unusual files.

Why it matters

The class is CWE-434, unrestricted upload of a file with a dangerous type. ZDI says the issue results from a lack of proper validation of user supplied data in email attachment handling. If an uploaded file can be placed somewhere the server will run it, an upload becomes code execution.

Help desk platforms handle content from many sources, including external email. That raises the stakes for any weakness in attachment handling, since the intake is meant to be open to anyone who can send a message.

Quick check

Do I need an account to exploit this?

Yes. The record and ZDI say authentication is required.

Which build is fixed?

BMC issued an update. We could not retrieve its article, so check it for the version.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.