CVE-2022-35865: This vulnerability allows remote attackers to execute arbitrary code on affected installations of BMC Track...
This vulnerability allows remote attackers to execute arbitrary code on affected installations of BMC Track-It! 20.21.2.109. Authentication is not required to exploit this vulnerability. The specific flaw exists within the authorization of HTTP requests. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-16709.
Security readout for executives and security teams
Plain-English summary
CVE-2022-35865 is an unauthenticated remote code execution issue in BMC Track-It! 20.21.2.109. A remote attacker could run code through exposed HTTP functionality and gain the privileges of the Track-It! service account. This is high urgency for any organization running the affected version.
Executive priority
Prioritize remediation where Track-It! is reachable from the internet or broad internal networks. The business risk is system compromise through a helpdesk platform without credentials, but available sources do not prove active exploitation.
Technical view
The flaw is CWE-306: missing authentication for critical functionality. ZDI and the CVE record describe improper authorization of HTTP requests, allowing unauthenticated network attackers to execute arbitrary code in the service account context. The CVSS 3.0 score is 7.3 with low attack complexity and no required user interaction.
Likely exposure
Exposure is limited to BMC Track-It! 20.21.2.109 installations, especially where the Track-It! HTTP interface is reachable from untrusted networks. The source bundle does not identify other affected versions.
Exploitation context
The sources support unauthenticated remote code execution, but the CVE is not listed as KEV in the provided bundle. There is no cited evidence here of active exploitation in the wild.
Researcher notes
Do not assume broader product impact beyond BMC Track-It! 20.21.2.109 from these sources. Patch details are referenced through BMC but not fully described in the bundle, so validation should anchor on the vendor advisory and deployed version evidence.
Mitigation direction
Identify all BMC Track-It! deployments and confirm exact versions.
Review BMC’s advisory for the vendor-approved patched version or workaround.
Apply the BMC-supported update path for affected Track-It! systems.
Restrict Track-It! HTTP access to trusted networks until remediated.
Review service account privileges and reduce unnecessary permissions.
Validation and detection
Check whether any Track-It! instance reports version 20.21.2.109.
Confirm whether the Track-It! HTTP interface is internet-accessible.
Verify the system has been updated according to BMC guidance.
Review logs for unexpected unauthenticated HTTP activity.
Confirm the Track-It! service account has limited privileges.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-306 · source CWE mapping
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.