dbcve.org
Track It\!Application · Bmc

CVE-2021-35001

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
BMC Track-It! GetData Missing Authorization Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of BMC Track-It!. Authentication is required to exploit this vulnerability. The specific flaw exists within the GetData endpoint. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-14527.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The GetData endpoint in BMC Track-It! lacks proper authorization checks, allowing authenticated users to access sensitive functionality they should not be permitted to use. This broken access control enables disclosure of stored credentials within the application.

MitigationApply vendor security patches for CVE-2021-35001; if unavailable, implement role-based access controls on the GetData endpoint and audit user permissions to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Track It\!Application
Affected:= 20.19.01= 20.19.02= 20.19.03= 20.20.01= 20.20.02= 20.20.03= 20.21.01

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if BMC Track-It! is installed
    Check the Windows Start Menu for BMC Track-It! programs, or look for the installation directory (commonly under C:\Program Files\BMC Software\Track-It! or C:\Inetpub\wwwroot\TrackIt).
    Affected if BMC Track-It! software is present on the system
  2. Verify the installed version
    Open Control Panel > Programs and Features, locate BMC Track-It!, and note the version column. Or check the Track-It! installation directory for a version file or check the About page within the application.
    Affected if The installed version matches 20.19.01, 20.19.02, 20.19.03, 20.20.01, 20.20.02, 20.20.03, or 20.21.01
  3. Confirm the GetData endpoint exists
    Check if the web application exposes a GetData endpoint. This is typically accessible via HTTP/HTTPS to the Track-It! web interface, often at paths like /Services/GetData.asmx or /api/GetData. Use a web browser or curl to attempt access to these URLs.
    Affected if The GetData endpoint is accessible and responds to requests
  4. Test authorization controls on the endpoint
    Log in to Track-It! with a standard user account (non-admin). Attempt to access the GetData endpoint directly via web request or by calling the API. Observe whether the endpoint returns sensitive data such as stored credentials without rejecting the request based on insufficient privileges.
    Affected if Authenticated standard users can retrieve sensitive data or credentials through the GetData endpoint that should be restricted to administrators only

A system is affected if it runs BMC Track-It! versions 20.19.01 through 20.21.01, has the GetData endpoint exposed, and allows lower-privileged authenticated users to access sensitive functionality or retrieve stored credentials through that endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor security patches for CVE-2021-35001; if unavailable, implement role-based access controls on the GetData endpoint and audit user permissions to limit exposure.

Fix this in Track It\! Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-35001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-35001 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data