CVE-1999-0118
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 · uneditedAIX infod allows local users to gain root access through an X display.
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 AIX infod daemon contains a vulnerability that allows local users to escalate privileges to root by exploiting the X display connection. The infod service improperly handles authentication or authorization when accessed through X11, enabling a local attacker to gain unauthorized root access.
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= 3.2= 4.1= 4.2= 4.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 AIX versionRun 'oslevel' command or check /etc/security/audit/config to determine the installed AIX versionAffected if Version matches 3.2, 4.1, 4.2, or 4.3
-
Determine if infod daemon is runningCheck the infod service status using 'lssrc -s infod' or 'ps -ef | grep infod' commandAffected if infod daemon is active and AIX version is among the affected versions
-
Verify X11 display access configurationCheck X display access controls using 'xhost' command or inspect .Xauthority file permissions in the user's home directoryAffected if X display access is permitted locally and infod daemon is running on an affected AIX version
-
Confirm infod X11 authentication handlingReview infod configuration files in /usr/lib/inst or /etc for X authentication settings, or check if infod accepts X display connections without proper authorizationAffected if infod permits X display connections without adequate authentication on an affected AIX version
A user is affected if they are running AIX versions 3.2, 4.1, 4.2, or 4.3 with the infod daemon active and X display access configured in a way that allows local users to trigger the privilege escalation.
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 the appropriate AIX security patch from IBM for this vulnerability. If patches are unavailable for the legacy system, disable the infod service and restrict X display access controls to prevent local privilege escalation.
- 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-0118 — 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-0118 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