dbcve.org
LibdmxApplication · X

CVE-2013-1992

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
Multiple integer overflows in X.org libdmx 1.1.2 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the (1) DMXGetScreenAttributes, (2) DMXGetWindowAttributes, and (3) DMXGetInputAttributes 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 libdmx's DMXGetScreenAttributes, DMXGetWindowAttributes, and DMXGetInputAttributes functions allow malicious X servers to trigger insufficient memory allocation, leading to buffer overflows. The vulnerability stems from improper validation of integer values used in memory allocation calculations.

MitigationUpgrade libdmx to version 1.1.3 or later, or apply the vendor security patch to properly validate integer values before memory allocation in the affected functions.

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
LibdmxApplication
Affected:<= 1.1.2= 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. Verify libdmx is installed
    Locate the libdmx library on the system. On Linux, search for libdmx files: find /usr -name '*dmx*' 2>/dev/null or check package manager: rpm -qa | grep -i dmx or dpkg -l | grep -i dmx
    Affected if libdmx library is present on the system
  2. Determine installed libdmx version
    Query the library version. Try: pkg-config --modversion libdmx, or check the package directly: rpm -q libdmx or dpkg -s libdmx, or examine the shared library: readelf -d /usr/lib/libdmx.so.1 2>/dev/null | grep version
    Affected if version is 1.0.2, 1.0.99.1, 1.1.0, 1.1.1, or any version <= 1.1.2 (not including 1.1.3)
  3. Confirm DMX extension is available
    Check if the DMX extension is compiled into the X server or loaded at runtime. Examine X server capabilities:xdpyinfo -display :0 2>/dev/null | grep -i dmx, or check for the DMX X extension module: ls /usr/lib/xorg/modules/extensions/libdmx* 2>/dev/null
    Affected if DMX extension is present and loadable by the X server
  4. Identify running DMX processes or configurations
    Look for active DMX usage or configuration files. Check for dmx* processes: ps aux | grep -i dmx, examine X configuration for DMX screen definitions: grep -r 'dmx' /etc/X11/xorg.conf* 2>/dev/null, or check for active X server with DMX backend connections
    Affected if DMX is actively configured or in use (system acts as a DMX frontend connecting to backend X servers)
  5. Assess network exposure to X servers
    Review network listening services and firewall rules for X server ports (typically 6000-6063 for TCP). Check: netstat -tlnp | grep -E '60[0-9]|x11', or verify if X servers accept TCP connections: grep -E '^(ListenAddress|Port)' /etc/X11/xorg.conf* 2>/dev/null
    Affected if X servers accept TCP connections from untrusted networks, increasing risk of malicious server interaction

A system is affected if it has libdmx version <= 1.1.2 (any of 1.0.2, 1.0.99.1, 1.1.0, 1.1.1, or earlier) AND the DMX extension is enabled or configured, creating a potential vector where a compromised X server could trigger the integer overflow in libdmx client functions.

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

Upgrade libdmx to version 1.1.3 or later, or apply the vendor security patch to properly validate integer values before memory allocation in the affected functions.

Fix this in Libdmx Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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