Skip to content
Fencer Vulns
critical 9.8

CVE-2018-19800 json

aubio Buffer Overflow vulnerability

published 2019-06-07 7 y ago modified 2026-06-17 4 mo ago also GHSA-grmf-4fq6-2r79 , PYSEC-2019-162 , EUVD-2019-0021

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

aubio v0.4.0 to v0.4.8 has a Buffer Overflow in new_aubio_tempo.

Patch / fix

  • pypi aubio 0.4.9
  • aubio Debian 14, Debian 13, Debian 12 0.4.9-1

debian advisories DEBIAN-CVE-2018-19800

  • aubio Package Hub 15 0.4.6-bp150.3.12.1
  • python-aubio Package Hub 15 0.4.6-bp150.3.12.1
  • aubio openSUSE Leap 15.1, openSUSE Leap 15.0 0.4.6-lp151.6.3.1
  • python-aubio openSUSE Leap 15.1, openSUSE Leap 15.0 0.4.6-lp151.6.3.1

opensuse advisories openSUSE-SU-2019:1624-1openSUSE-SU-2019:1618-1

  • aubio Arch Linux 0.4.9-1

arch linux advisories AVG-888

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-2018-19800 updated cvss 5.3

aubio: new_aubio-tempo feature causing buffer overflow

  • 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

2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi aubio
>=0.4.0, <0.4.9
0.4.9

Classification

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

References

Sources

Fencer Vulns 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.