dbcve.org
Libxxf86vmApplication · X

CVE-2013-2001

MEDIUM · 6.8 CVSS v2.0 Published 2013-06-15
Fix available
A fix is available. Upgrade to after 1.1.2 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
Buffer overflow in X.org libXxf86vm 1.1.2 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 XF86VidModeGetGammaRamp 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 confidence

Buffer overflow vulnerability in libXxf86vm (versions 1.1.2 and earlier) within the XF86VidModeGetGammaRamp function. The flaw allows remote attackers to trigger the overflow via crafted length or index values, potentially causing denial of service (crash) or arbitrary code execution.

MitigationUpdate libXxf86vm to a version later than 1.1.2, or if the extension is not required, disable the XFree86-VidModeExtension in the X server configuration.

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
Libxxf86vmApplication
Affected:<= 1.1.2= 1.0.1= 1.0.2= 1.0.99.1= 1.1.0= 1.1.1

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 libXxf86vm library version
    Run 'pkg-config --modversion xxf86vm' or check the installed package via your system's package manager (dpkg -l libxxf86vm, rpm -q libXxf86vm, etc.)
    Affected if The reported version is 1.1.2 or earlier, or matches 1.0.1, 1.0.2, 1.0.99.1, 1.1.0, or 1.1.1
  2. Locate the libXxf86vm library file
    Use 'ldconfig -p | grep -i xxf86vm' or find /usr/lib*/libXxf86vm.so* to locate the shared library
    Affected if The library file exists on the system, indicating the component is installed
  3. Verify XF86VidMode extension availability
    Run 'xdpyinfo' or check X server logs for 'XF86VidMode' extension entries, or use 'xrandr --verbose' which may invoke the extension
    Affected if The XF86VidMode extension is reported as available or enabled by the X server

If the installed libXxf86vm version is 1.1.2 or earlier (specifically 1.0.1 through 1.1.2) and the XF86VidMode extension is present in the X server, the environment is affected by this vulnerability.

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

Update libXxf86vm to a version later than 1.1.2, or if the extension is not required, disable the XFree86-VidModeExtension in the X server configuration.

Fix this in Libxxf86vm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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