Skip to content
Fencer Intel
medium 6.8

CVE-2013-6369 json

Stack-based buffer overflow in the jbg_dec_in function in libjbig/jbig.c in JBIG-KIT before 2.1 allows remote attackers to cause a denial o…

published 12y ago modified 4mo ago also EUVD-2013-6194

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

Summary

Stack-based buffer overflow in the jbg_dec_in function in libjbig/jbig.c in JBIG-KIT before 2.1 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a crafted image file.

Patch / fix

  • jbigkit Debian 14, Debian 13, Debian 12 2.0-2.1

debian advisories DEBIAN-CVE-2013-6369

  • jbigkit Ubuntu 14.04 LTS 2.0-2ubuntu4.1

ubuntu advisories UBUNTU-CVE-2013-6369

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • jbigkit openSUSE Tumbleweed 2.1-3.8

opensuse advisories openSUSE-SU-2024:10541-1

Is CVE-2013-6369 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-6369 updated cvss 4.4

jbigkit: stack-based buffer overflow flaw

  • Red Hat Enterprise Linux 7 jbigkit, jbigkit-libs
    not affected: vulnerable code not present

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

3.45% chance of exploitation in the next 30 days, higher than 89% 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.