CVE-2013-1990
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 · uneditedMultiple integer overflows in X.org libXvMC 1.0.7 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the (1) XvMCListSurfaceTypes and (2) XvMCListSubpictureTypes 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 confidenceInteger overflow vulnerabilities in libXvMC's XvMCListSurfaceTypes and XvMCListSubpictureTypes functions allow a malicious X server to cause insufficient memory allocation, leading to buffer overflows when processing video surface and subpicture type requests.
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.
-
Identify installed libxvmc versionRun 'dpkg -l libxvmc1' on Debian/Ubuntu, 'rpm -q libxvmc' on RHEL/CentOS, or check /usr/lib/libXvMC.so.* for the library version fileAffected if The installed version is 1.0.7 or earlier (specifically 1.0.2 through 1.0.7)
-
Confirm library file presenceLocate libXvMC shared library with 'find /usr -name "libXvMC*" 2>/dev/null' or 'ldconfig -p | grep -i xvmc'Affected if The library exists on the system, indicating XvMC support is compiled in
-
Check if XvMC client applications are in useSearch for running processes using XvMC with 'ps aux | grep -i xmvp' or review application dependencies for libXvMC usageAffected if Applications that link against libXvMC are running and connecting to X servers
-
Verify X server exposureCheck X server configuration with 'xdpyinfo' or review /etc/X11/xorg.conf for X server settings; note if the system runs a local X server or connects to remote X serversAffected if The system runs an X server that could be exploited, or connects to untrusted remote X servers
You are affected if libxvmc version 1.0.7 or earlier is installed AND applications using libXvMC are running in an environment where they communicate with potentially malicious X servers.
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 X.org libXvMC to version 1.0.8 or later to patch the integer overflows. Verify no vulnerable versions remain in any X server deployments.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1990 — 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-1990 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