CVE-2013-2002
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 · uneditedBuffer overflow in X.org libXt 1.1.3 and earlier allows X servers to cause a denial of service (crash) and possibly execute arbitrary code via crafted length or index values to the _XtResourceConfigurationEH 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 · high confidenceBuffer overflow in X.org libXt library (versions 1.1.3 and earlier) in the _XtResourceConfigurationEH function allows X servers to crash or potentially execute arbitrary code via crafted length or index values.
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.1.3= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1.1= 1.1.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
- 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 libXt versionRun 'pkg-config --modversion libxt' on Linux systems, or check the library directly with 'rpm -q libXt' (RHEL/CentOS) or 'dpkg -l libXt' (Debian/Ubuntu). On Solaris, use 'pkginfo | grep libXt'. On HP-UX, use 'swlist | grep libXt'. Alternatively, examine the library file directly: 'ls -la /usr/lib/libXt*' and check any version indicators in the file name or associated package metadata.Affected if The installed version is 1.1.3 or earlier, or specifically 1.0.3 through 1.0.9, 1.1.1, or 1.1.2.
-
Confirm X server is in useCheck if an X server is running by executing 'ps aux | grep X' or 'systemctl status display-manager' (systemd) or 'svcs -a | grep x11' (Solaris). Also verify X-related processes such as Xorg, XFree86, or display manager daemons like gdm, kdm, lightdm, or xdm.Affected if An X server is active and loading the libXt library.
-
Verify libXt library is linked to X serverRun 'ldd $(which Xorg)' or 'ldd $(which X)' to see if libXt is loaded. On AIX, use 'ldd /usr/bin/X' instead. Check the output for libXt.so.* to confirm the library is in use by the X server process.Affected if The X server binary links against the vulnerable libXt library version.
-
Check for application-specific X clients using libXtIdentify any running X client applications that link to libXt by running 'ldd' on X-related binaries in /usr/bin or /usr/X11/bin. Applications using Motif or Xt-based toolkits may load this library at runtime.Affected if Client applications using libXt are running and connecting to a potentially vulnerable X server.
You are affected if the installed libXt version is 1.1.3 or earlier (including 1.0.3 through 1.0.9, 1.1.1, or 1.1.2) and an X server or X client application is actively using that library.
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 dataUpgrade libXt to a patched version (1.1.4 or later). If immediate patching is not feasible, restrict X server access to trusted users and networks to reduce attack surface.
- Consultation3.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2002 — 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-2002 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