CVE-1999-0149
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 wrap CGI program in IRIX allows remote attackers to view arbitrary directory listings 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 confidenceA path traversal vulnerability in the wrap CGI program on IRIX (Silicon Graphics' Unix variant) allows remote attackers to access arbitrary directory listings by using '../' sequences in HTTP requests to escape the intended 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 data= 6.2CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/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.
-
Confirm the operating system is SGI IRIXRun 'uname -a' or check /etc/issue to verify the OS is SGI IRIXAffected if The system is not SGI IRIX, so it is not affected by this specific vulnerability
-
Verify the IRIX version is 6.2Run 'uname -r' or check the IRIX release version. Compare your installed version against the affected range (= 6.2)Affected if Version is exactly 6.2, matching the affected version listed
-
Locate the wrap CGI programSearch for the wrap CGI binary in common web directories such as /cgi-bin/ or /usr/sgi/_bin/ using the 'find' command (e.g., find / -name wrap -type f 2>/dev/null)Affected if The wrap CGI program exists on the system
-
Confirm the web server is runningCheck if a web server is running and serving CGI scripts by examining running processes (ps -ef | grep httpd) or checking if port 80 is listening (netstat -an | grep 80)Affected if A web server is active and serving requests on the system
-
Test for path traversal accessIf the wrap CGI is accessible via web, send an HTTP request containing '../' sequences (for example: GET /cgi-bin/wrap?../../../etc HTTP/1.0) to see if directory listings outside the web root can be retrievedAffected if The request returns directory listings or files outside the intended web root, confirming the vulnerability is present
A system is affected if it is running SGI IRIX version 6.2 with the wrap CGI program present and accessible through an active web server that allows path traversal sequences to escape the web root.
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 dataDisable or remove the vulnerable wrap CGI program if patches are unavailable; implement strict input validation to reject path traversal sequences in URL parameters.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0149 — 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-0149 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