Skip to content
Fencer Intel
low 3.3

CVE-2019-19004 json

A biWidth*biBitCnt integer overflow in input-bmp.c in autotrace 0.31.1 allows attackers to provide an unexpected input value to malloc via…

published 5y ago modified 4mo ago also EUVD-2019-8657

cvss
3.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits
0
none known

Summary

A biWidth*biBitCnt integer overflow in input-bmp.c in autotrace 0.31.1 allows attackers to provide an unexpected input value to malloc via a malformed bitmap image.

Patch / fix

  • autotrace RHEL 8 0.31.1-53.el8

red hat advisories RHSA-2021:4519

  • autotrace AlmaLinux 8 0.31.1-53.el8

almalinux advisories ALSA-2021:4519

Is CVE-2019-19004 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-2019-19004 updated cvss 3.3

autotrace: integer overflow in input-bmp.c

  • Red Hat Enterprise Linux 6 autotrace Red Hat Enterprise Linux 7 autotrace
    affected: no fix planned “Out of support scope”
  • Red Hat CodeReady Linux Builder (v. 8) autotrace 0.31.1-53.el8
    fixed: vendor fix RHSA-2021:4519

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.03% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 3.3 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-190 Integer Overflow or Wraparound

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.