CVE-1999-1404
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 · uneditedIBM/Tivoli OPC Tracker Agent version 2 release 1 allows remote attackers to cause a denial of service (resource exhaustion) via malformed data to the localtracker client port (5011), which prevents the connection from being closed properly.
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 · moderate confidenceThe IBM/Tivoli OPC Tracker Agent v2.1 fails to properly close client connections to port 5011 when receiving malformed data. This leaves connections in an open state, causing resource exhaustion (likely memory or connection handle depletion) and leading to denial of service.
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= 1.0x= 2.0x= 3.0xCVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM/Tivoli OPC Tracker Agent installationSearch for the OPC Tracker Agent software on the system using system inventory tools, package managers, or by checking common installation directories for Tivoli software.Affected if The software is present on the system.
-
Determine installed versionCheck the version of the installed IBM/Tivoli OPC Tracker Agent by querying installed software listings, examining the executable properties, or reviewing product documentation.Affected if The version matches 1.0x, 2.0x, or 3.0x.
-
Identify if port 5011 is listeningRun a network port scan or use commands such as 'netstat -an' or 'ss -tlnp' to check if port 5011 is in LISTEN state on any network interface.Affected if Port 5011 is open and listening.
-
Assess network exposure of the serviceDetermine if the system hosting the OPC Tracker Agent is accessible from network segments where untrusted users could send malformed data to port 5011. Check firewall rules, networkACLs, and binding addresses (e.g., 0.0.0.0 vs 127.0.0.1).Affected if Port 5011 is exposed to untrusted network paths.
A user is affected if IBM/Tivoli OPC Tracker Agent versions 1.0x, 2.0x, or 3.0x are installed with port 5011 exposed to the network.
Generated from the published advisory. Verify against your own configuration.
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 dataSince this is legacy software from 1999, primary options include: (1) upgrading to a supported version if available, (2) restricting network access to port 5011 via firewall rules to prevent unauthorized remote exploitation, or (3) implementing connection timeout policies at the network boundary.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1404 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-1404 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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