CVE-1999-1067
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 · uneditedSGI MachineInfo CGI program, installed by default on some web servers, prints potentially sensitive system status information, which could be used by remote attackers for information gathering activities.
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 SGI MachineInfo CGI program, installed by default on certain web servers, exposes potentially sensitive system status information when accessed remotely. This information disclosure could aid attackers in reconnaissance activities by revealing server configuration, hardware details, or system state.
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.3CVSS 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.
-
Identify the operating system and versionRun 'uname -a' or check /etc/os-release (if available on IRIX) to confirm the system is SGI IRIX version 6.3Affected if The system is running SGI IRIX 6.3 specifically
-
Locate the MachineInfo CGI scriptSearch for a file named 'MachineInfo' or 'machineinfo' in the web server's cgi-bin directory, typically found under /cgi-bin/ or /httpd/cgi-bin/Affected if The MachineInfo CGI script exists on the system
-
Check if the web server serves CGI scriptsExamine the web server configuration (httpd.conf or equivalent) to determine if CGI execution is enabled for the cgi-bin directoryAffected if CGI scripts are enabled and the MachineInfo script is in an executable directory
-
Verify remote access to the MachineInfo CGIAttempt to access http://localhost/cgi-bin/MachineInfo or the equivalent URL on the web server to see if the script executes and returns system informationAffected if The URL returns system status, configuration, or hardware details
-
Confirm the sensitivity of information disclosedReview the output from the MachineInfo CGI to determine if it exposes server configuration, hardware details, or system state that should not be publicly visibleAffected if The script reveals sensitive system information to remote requesters
A system is affected if it runs SGI IRIX 6.3 with the MachineInfo CGI script present and accessible via the web server, allowing remote attackers to obtain sensitive system status information.
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 dataRemove or disable the MachineInfo CGI script from the web server's cgi-bin directory, or restrict access to it via web server authentication or access controls.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-1067 — 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-1067 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