Skip to content
Fencer Intel
medium 6.8

CVE-2013-1996 json

X.org libFS 1.0.4 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to an…

published 2013-06-15 13 y ago modified 2026-06-16 4 mo ago also EUVD-2013-1984

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

X.org libFS 1.0.4 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to an unexpected sign extension in the FSOpenServer function.

Patch / fix

  • libfs Debian 14, Debian 13, Debian 12 2:1.0.4-1+deb7u1

debian advisories DEBIAN-CVE-2013-1996

  • libFS openSUSE Tumbleweed 1.0.7-1.8

opensuse advisories openSUSE-SU-2024:10068-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-1996 updated cvss 4.3

libFS: Sign extension issues resulting in heap-based buffer overflow

  • Red Hat Enterprise Linux 5 libFS
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.26% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.