CVE-2016-6599

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

CVSS 3.09.8Critical EPSS percentile96th12% chance in 30 days CISA KEVNot listedNo confirmed exploitation
Public exploit: 3 sources FixVendor fixNo build named by the sources

Published 2018-01-30Updated 2024-11-21Sources: CVE.org, NVD

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record

Check whether your BMC Track-It! installation is running Track-It! 11.4 and whether Hotfix 3 (or later) is applied.
From the network perspective, verify whether port 9010 on the Track-It! server is reachable from untrusted networks (for example, the internet or other business network segments not tightly controlled).
If either (a) you are on Track-It! 11.4 without Hotfix 3 or (b) port 9010 is reachable from untrusted networks, plan an immediate upgrade to the vendor-fixed update: Track-It! 11.4 Hotfix 3 (or later).
After patching, re-check that port 9010 is no longer exposed to untrusted networks (or is restricted to only the required internal management paths).

Vendor advisory Some work to apply

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

BMC Track-It! 11.4 before Hotfix 3 exposes an unauthenticated .NET remoting configuration service (ConfigurationService) on port 9010. This service contains a method that can be used to retrieve a configuration file that contains the application database name, username and password as well as the domain administrator username and password. These are encrypted with a fixed key and IV ("NumaraIT") using the DES algorithm. The domain administrator username and password can only be obtained if the Self-Service component is enabled, which is the most common scenario in enterprise deployments.

In plain language

Written by AI from the record

If you run BMC Track-It! 11.4, versions before Hotfix 3 may expose a configuration service to the network that can allow an attacker to retrieve sensitive configuration data (including database and administrative credentials). This is a serious risk for businesses where the service is reachable from outside the office network, so you should check and patch.

Unauthenticated .NET remoting ConfigurationService in BMC Track-It! 11.4 (before Hotfix 3) is exposed on port 9010, allowing remote callers to retrieve an exported configuration file containing database and administrator credentials protected by a fixed DES key/IV.

If you're affected

Database credential theft
Domain admin credential theft
Full system compromise risk
Service disruption risk

What is it

Think of this as a hidden “settings” doorway on your Track-It! server that does not properly require a lock. If someone can reach it over the network, they may be able to pull out a copy of sensitive configuration details—like usernames and passwords—stored inside the system’s own configuration file. With those credentials, an attacker can potentially log in and take over other parts of your IT environment.

Who is affected

This matters if you run BMC Track-It! 11.4 and your installation is older than Hotfix 3. It’s especially important when your Track-It! server’s port 9010 is reachable from beyond tightly trusted internal networks. Reachability is the gate: if attackers can’t reach that service over the network, the risk is greatly reduced.

How urgent is it

Treat this as urgent because the issue involves an exposed service that does not require authentication, and public proof-of-concept code exists. Even though it is not listed in CISA KEV, the combination of remote access and credential exposure makes it a high-priority patch candidate (consistent with an AMBER risk level).

What to do — in detail

Confirm your exposure (what to check):
- Identify the exact BMC Track-It! version installed.
- Confirm whether “Hotfix 3” is installed for Track-It! 11.4.
- Check network exposure of the Track-It! host: determine whether TCP port 9010 is reachable from any untrusted source (for example, internet-facing networks, guest networks, or other teams/segments that you do not explicitly trust).
Determine if you’re in the affected version range:
- This CVE applies to BMC Track-It! 11.4 “before Hotfix 3.”
Apply the vendor fix:
- Upgrade Track-It! to the vendor remediation referenced by BMC’s Track-It! security advisory (24-Dec-2015).
- Target outcome: Track-It! 11.4 Hotfix 3 (or later) installed.
Temporary workaround if patching is delayed:
- Restrict network access to port 9010 so it is only accessible from the systems/administrative networks that truly require it.
- If you can’t restrict inbound access safely, consider placing the Track-It! server behind a firewall/VPN so untrusted networks cannot reach port 9010.
Post-change verification:
- Reconfirm that Hotfix 3 (or later) is present.
- Re-test (from an untrusted network viewpoint, or using your security scanner) that port 9010 is not reachable from untrusted networks.
What to monitor:
- Look for unusual access patterns against the Track-It! host around the time of exposure/patching.
- If you have logs for service calls, review for requests consistent with configuration-service access.
KEV due date:
- Not provided because this CVE is not listed in CISA KEV in the provided findings.

Technical context

Severity is high based on remote, unauthenticated access to a configuration service containing sensitive credential material. The weakness is CWE-255 (path traversal/credential exposure style weaknesses are often miscategorized across advisories; in this case the practical impact is exposure of sensitive configuration/credentials). Mechanism: BMC Track-It! 11.4 (before Hotfix 3) exposes an unauthenticated .NET remoting ConfigurationService on port 9010; it can be used to retrieve an exported configuration file that contains database connection details (database name, username, password) and domain administrator credentials. The sensitive data is encrypted with a fixed key/IV (“NumaraIT”) using the DES algorithm, which undermines the protection. Exploitation status: public proof-of-concept exists (3 known), but it is not in the CISA KEV list based on the provided findings, so KEV-confirmed exploitation is not asserted here. EPSS is provided as a prediction only (and not repeated publicly).

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS96th

Public exploit

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

3 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in

EPSS

12% chance of exploitation activity in the next 30 days, which ranks it in the 96th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Rising.

Lifecycle

The patch came 471 days before any public exploit.

2026-09-23EPSS band changelow → moderateepss band change
2026-09-21EPSS band changemoderate → lowepss band change
2026-09-06EPSS band changelow → moderateepss band change
2026-09-05EPSS band changemoderate → lowepss band change
2026-08-31EPSS band change0 → moderateepss band change
2026-08-29EPSS band changemoderate → low

Affected products

bmccommercial · USaka control-m, patrol agent, track-it!
- track-it\!Web AppOn-premEnterprise Software / itsm-monitoring

And 1 more affected product. See all after sign-in

Technical detail

CVSS 3.0 vector

Open in the CVSS calculator

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

Scored 9.8 by NVD.

How it is reached

Attack Vector NetworkExploitable remotely over the network without any special conditions
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

CWE-255No name in the record

Sources

References in the record

And 1 more reference. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Track-it\!, not every advisory. This one: public exploit.

A free account adds

The full version matrix and every affected product
Exploit links, proofs of concept and Metasploit modules
Email alerts for the products you watch
The same data over REST API, MCP and CLI

Create a free account