dbcve.org
LibxpApplication · X

CVE-2013-2062

MEDIUM · 6.8 CVSS v2.0 Published 2013-06-15
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Multiple integer overflows in X.org libXp 1.0.1 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the (1) XpGetAttributes, (2) XpGetOneAttribute, (3) XpGetPrinterList, and (4) XpQueryScreens functions.

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 confidence

Integer overflows in libXp's XpGetAttributes, XpGetOneAttribute, XpGetPrinterList, and XpQueryScreens functions allow malicious X servers to cause insufficient memory allocation, leading to heap-based buffer overflows and potential code execution.

MitigationUpdate libXp to a patched version. If the library is unused, remove or disable it. Restrict X server connections to trusted sources.

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
LibxpApplication
Affected:<= 1.0.1= 1.0.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if libXp library is installed
    On Linux, run `rpm -qa | grep -i libXp` (RHEL/CentOS) or `dpkg -l | grep -i libxp` (Debian/Ubuntu). On Solaris, run `pkginfo | grep -i libXp`. Alternatively, search for the library file with `find /usr -name 'libXp.so*' 2>/dev/null`.
    Affected if The library package or libXp.so file is found on the system
  2. Determine the installed libXp version
    If using rpm-based systems, run `rpm -q --qf '%{VERSION}-%{RELEASE}' libXp`. For dpkg systems, run `dpkg -s libxp`. Compare the version number against the affected range: versions 1.0.0 and 1.0.1 (or any version <= 1.0.1) are vulnerable.
    Affected if The installed version is 1.0.0, 1.0.1, or any version up to and including 1.0.1
  3. Verify if X Print (Xp) extension is enabled
    Check X server configuration files (typically /etc/X11/xorg.conf or files in /etc/X11/xorg.conf.d/) for the presence of the Load "Xp" directive or any PrintExtension configuration. Also check Xorg log files (typically /var/log/Xorg.0.log) for lines containing "Xp" or "X-PRINT".
    Affected if The X Print extension is loaded or configured in the X server, as the vulnerable functions belong to this extension
  4. Identify processes using libXp
    Run `ldd $(which X) 2>/dev/null | grep -i libXp` to check if the X server links to libXp. Alternatively, use `find /proc -maxdepth 2 -name maps -exec grep -l libXp {} \; 2>/dev/null` to find processes with libXp loaded in memory.
    Affected if The X server or any X client application is actively using libXp (the library is loaded into memory)
  5. Check for untrusted X server connections
    Review X server access control settings by running `xhost` (if X tools are available) and check firewall rules or /etc/hosts.allow/hosts.deny for X connections. The vulnerability is triggered by malicious X servers, so external or untrusted X connections increase exposure.
    Affected if The system accepts X connections from untrusted or network sources (xhost shows + or permissive access control)

The system is affected if libXp version 1.0.0 or 1.0.1 (or any version <= 1.0.1) is installed AND the X Print extension is being used by the X server or applications, particularly if untrusted X connections are allowed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Update libXp to a patched version. If the library is unused, remove or disable it. Restrict X server connections to trusted sources.

Fix this in Libxp Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-2062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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