CVE-2013-1995
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 · uneditedX.org libXi 1.7.1 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to an unexpected sign extension in the XListInputDevices function.
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 confidenceA buffer overflow vulnerability in X.org libXi 1.7.1 and earlier allows malicious X servers to trigger insufficient memory allocation via an unexpected sign extension flaw in the XListInputDevices function, potentially leading to memory corruption.
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<= 1.7.1= 1.5.0= 1.5.99.2= 1.5.99.3= 1.6.0= 1.6.1= 1.6.2= 1.6.99.1= 1.7CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify installed libXi versionRun 'pkg-config --modversion xi' or check the library file: 'ls -la /usr/lib/libXi.so*' and compare to the affected versions listed in the CVEAffected if Installed version is 1.7.1 or earlier, or matches any of these: 1.5.0, 1.5.99.2, 1.5.99.3, 1.6.0, 1.6.1, 1.6.2, 1.6.99.1, or 1.7
-
Verify XListInputDevices is in useSearch application binaries or libraries that link against libXi and call XListInputDevices: 'nm -D /usr/lib/libXi.so.6 | grep XListInputDevices' or 'ldd <binary> | grep Xi'Affected if Applications or libraries linked against libXi call the XListInputDevices function, which is the vulnerable code path
-
Check for untrusted X server connectionsInspect X11 configuration: review 'xauth list' and X server access controls (xhost), or check if the X server listens on network interfaces rather than only localhostAffected if The system runs an X server that accepts connections from untrusted clients, or runs X clients that connect to untrusted X servers, enabling the malicious X server attack vector
A system is affected if it runs any version of libXi <= 1.7.1 and utilizes the XListInputDevices function in an environment where untrusted X servers can connect.
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 dataUpdate X.org libXi to version 1.7.2 or later to patch the sign extension vulnerability in XListInputDevices.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1995 — 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-2013-1995 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