dbcve.org
Debian LinuxOperating system · Debian

CVE-2013-2064

MEDIUM · 6.8 CVSS v2.0 Published 2013-06-15
Fix available
A fix is available. Upgrade to after 1.9 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
Integer overflow in X.org libxcb 1.9 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the read_packet 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 confidence

Integer overflow in libxcb's read_packet function allows a malicious X server to trigger insufficient memory allocation, leading to a buffer overflow. This affects libxcb 1.9 and earlier versions, enabling remote code execution or denial of service against X clients.

MitigationUpdate libxcb to a version newer than 1.9 (patched versions address the integer overflow in read_packet). Inventory all systems and applications linking against libxcb and apply the update.

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
Debian LinuxOperating system
Affected:= 6.0= 7.0
Ubuntu LinuxOperating system
Affected:= 10.04= 12.04= 12.10= 13.04
FedoraOperating system
Affected:= 19
Secure Global DesktopApplication
Affected:= 4.71= 5.2
OpensuseOperating system
Affected:= 12.2= 12.3
LibxcbApplication
Affected:<= 1.9= 1.1.90.1= 1.1.91= 1.1.92= 1.1.93= 1.2= 1.3= 1.4= 1.5= 1.6= 1.7= 1.8

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. Identify installed libxcb version
    Run 'dpkg -l libxcb1' on Debian/Ubuntu, 'rpm -q libxcb' on Fedora/RHEL, or check the library file directly with 'ldd --version' or inspect /usr/lib/x86_64-linux-gnu/libxcb.so.1'
    Affected if The installed version is 1.9 or earlier, or matches any of these specific versions: 1.1.90.1, 1.1.91, 1.1.92, 1.1.93, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7, or 1.8
  2. Find applications linking against libxcb
    Use 'ldconfig -p | grep libxcb' to list libraries, or run 'find /usr -name "*.so*" -exec ldd {} \; 2>/dev/null | grep libxcb' to find linked binaries, or check application dependencies with 'obj -p <binary> 2>/dev/null'
    Affected if Any application or service on the system is linked against a vulnerable libxcb version and accepts connections from or communicates with X servers
  3. Determine if X client functionality is in use
    Check for running X client applications with 'ps aux | grep -E "(xterm|firefox|chrome|gnome|kde|X11)" ' or check for X11 display environment with 'echo $DISPLAY'
    Affected if The system runs any X client applications or has DISPLAY set, indicating X server communication that could trigger the vulnerable read_packet code path
  4. Verify X server connectivity
    Review network connections or Unix sockets listening for X11 with 'ss -ltnp | grep -E "(6000|x11)"' or check /tmp/.X11-unix sockets
    Affected if The system connects to untrusted X servers or accepts X connections from network sources, enabling a malicious X server to exploit the integer overflow in read_packet

The environment is affected if a vulnerable libxcb version (1.9 or earlier, or listed affected versions) is installed and any X client application using libxcb can receive data from an untrusted or potentially compromised X server.

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.9
Interim mitigation

Update libxcb to a version newer than 1.9 (patched versions address the integer overflow in read_packet). Inventory all systems and applications linking against libxcb and apply the update.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-2064 — 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-2064 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