CVE-1999-0036
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 · uneditedIRIX login program with a nonzero LOCKOUT parameter allows creation or damage to files.
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 IRIX login program contains a vulnerability where a nonzero LOCKOUT parameter value allows unauthorized file creation or file system damage. This appears to be a flaw in how the login program handles the LOCKOUT configuration, potentially allowing local privilege escalation or arbitrary file manipulation.
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= 5.1= 5.2= 5.3= 6.0= 6.1= 6.2= 6.3= 6.4CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 IRIX versionRun 'uname -a' or 'cat /etc/issue' to determine the exact IRIX version numberAffected if The version matches 5.1, 5.2, 5.3, 6.0, 6.1, 6.2, 6.3, or 6.4
-
Locate the login programCheck for the presence of /bin/login or /usr/bin/login using 'ls -la /bin/login /usr/bin/login'Affected if The login program exists on the system and the IRIX version is in the affected range
-
Examine the login configuration for LOCKOUT parameterCheck login configuration files in /etc or /usr/etc for LOCKOUT settings, typically in /etc/login.conf or similar configuration files used by the login programAffected if A LOCKOUT parameter is configured with a nonzero value in the login configuration
-
Verify the vulnerability conditionReview the login configuration to determine if LOCKOUT is set to any value greater than zero, which enables the vulnerable code pathAffected if LOCKOUT is set to a nonzero numeric value in the login configuration
The system is affected if it runs IRIX versions 5.1 through 6.4 and the login program has a nonzero LOCKOUT parameter configured, allowing unauthorized file creation or file system manipulation.
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 any historical SGI (Silicon Graphics) patches for this vulnerability. For systems that cannot be patched, implement compensating controls such as restricting physical access, monitoring file system changes, and considering migration off the deprecated IRIX platform.
- Consultation8.0 h
- Implementation4.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,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0036 — 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-0036 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