Skip to content
Fencer Intel
high 7.8

CVE-2019-19918 json

Lout 3.40 has a heap-based buffer overflow in the srcnext() function in z02.c.

published 6y ago modified 4mo ago also EUVD-2019-9509

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

Summary

Lout 3.40 has a heap-based buffer overflow in the srcnext() function in z02.c.

Patch / fix

  • lout openSUSE Tumbleweed 3.42-1.3
  • lout Package Hub 15 SP2 3.40-bp152.4.3.1
  • lout Package Hub 15 SP1 3.40-bp151.2.3.1
  • lout openSUSE Leap 15.1 3.40-lp151.2.3.1
  • lout openSUSE Leap 15.2 3.40-lp152.3.3.1

opensuse advisories openSUSE-SU-2024:11027-1openSUSE-SU-2020:1813-1openSUSE-SU-2020:1812-1openSUSE-SU-2020:1772-1openSUSE-SU-2020:1771-1

  • lout Arch Linux 3.41-1

arch linux advisories AVG-1934

Is CVE-2019-19918 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-19918 updated cvss 6.6

lout: heap-based buffer overflow in srcnext in z02.c

  • Red Hat All currently supported Red Hat products
    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

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

Exploits and checks

  • lists.gnu.org https://lists.gnu.org/archive/html/lout-users/2019-12/msg00001.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness

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.