CVE-1999-0771
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 · uneditedThe web components of Compaq Management Agents and the Compaq Survey Utility allow a remote attacker to read arbitrary files via a .. (dot dot) attack.
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 confidenceThe web components of Compaq Management Agents and Compaq Survey Utility contain a directory traversal vulnerability that allows remote attackers to read arbitrary files on the system by using '..' sequences in HTTP requests to navigate outside the web root directory.
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 dataall versions= 2.0CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Check if Compaq Management Agents are installedLook for Compaq Management Agents software on the system. On Windows, check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Compaq or examine Program Files for Compaq directories. On Unix/Linux, check for /opt/compaq or similar directories.Affected if Compaq Insight Management Agent or Compaq Power Management software is present on the system
-
Identify if the web component is enabledCheck if the Compaq web server/service is running. Look for processes like 'hpwebagent', 'cmas', or port 2301 (common Compaq web agent port). Use 'netstat -an' to check for listening services on ports 2301, 80, or 443.Affected if The Compaq web management interface is running and accepting HTTP connections
-
Verify the version of Compaq Power ManagementIf Compaq Power Management version 2.0 is installed, check the installed version through the software inventory or version information in the program files or registry.Affected if Compaq Power Management version 2.0 is installed (all versions of Compaq Insight Management Agent are affected)
-
Test for directory traversal vulnerabilitySend an HTTP request to the web interface containing '../' sequences, such as 'GET /..//..//..//winnt/win.ini HTTP/1.1' or 'GET /..//..//etc/passwd HTTP/1.1' to the server on the affected port.Affected if The web server returns file contents outside the web root directory, confirming the directory traversal flaw is present
The system is affected if Compaq Insight Management Agent (any version) or Compaq Power Management 2.0 is installed with the web component enabled and accessible.
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 dataApply vendor patches for Compaq Management Agents if available; otherwise, disable or remove the vulnerable web components, implement network segmentation to restrict access, and consider migrating to modern server management solutions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0771 — 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-0771 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