CVE-2013-1999
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 libXvMC 1.0.7 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 XvMCGetDRInfo 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 vulnerability in X.org libXvMC 1.0.7 and earlier allows X servers to trigger the issue via crafted length or index values passed to the XvMCGetDRInfo function, potentially causing denial of service or arbitrary code execution.
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.0.7= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6CVSS 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.
-
Check if libXvMC library is installedRun 'pkg-config --modversion libxvvmc' or 'dpkg -l | grep libxvvmc' (Debian) or 'rpm -q libXvMC' (RHEL) to query the installed package versionAffected if Package version is 1.0.7 or earlier, or if the package name matches any of the affected versions (1.0.2 through 1.0.7)
-
Verify the exact libXvMC version numberUse 'ldd /path/to/Xorg 2>/dev/null | grep -i xvmc' to see if libXvMC is linked, then check the library file directly with 'strings /usr/lib*/libXvMC* 2>/dev/null | grep -i "XvMC"' or check the package metadata with your system's package managerAffected if The installed version is 1.0.7 or lower (1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, or 1.0.7)
-
Confirm XvMC extension is loaded in X serverRun 'xdpyinfo | grep -i xvmc' or check /var/log/Xorg.0.log for lines containing 'XvMC' to see if the extension is activeAffected if XvMC extension is reported as available or loaded in the X server
-
Identify processes using XvMC functionalityRun 'ps aux | grep -i x' and then check loaded libraries with 'cat /proc/<pid>/maps | grep -i xvmc' for any X client applications that may be calling XvMCGetDRInfoAffected if Any application is actively using libXvMC functions, particularly XvMCGetDRInfo
You are affected if libXvMC version 1.0.7 or earlier (1.0.2-1.0.7) is installed AND the XvMC extension is enabled or any application is using the vulnerable 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 dataUpdate libXvMC to a version later than 1.0.7. If patching is not immediately feasible, restrict X server access to trusted clients only and monitor for anomalous XvMC API calls.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1999 — 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-1999 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