Skip to content
Fencer Intel
high 7.5

CVE-2019-16095 json

Symonics libmysofa 0.7 has an invalid read in getDimension in hrtf/reader.c.

published 7y ago modified 4mo ago also EUVD-2019-6941

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

Summary

Symonics libmysofa 0.7 has an invalid read in getDimension in hrtf/reader.c.

Patch / fix

  • libmysofa Debian 14, Debian 13, Debian 12 0.8~dfsg0-1

debian advisories DEBIAN-CVE-2019-16095

  • libmysofa Ubuntu 18.04 LTS 0.6~dfsg0-3+deb10u1build1

ubuntu advisories UBUNTU-CVE-2019-16095

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

  • libmysofa Package Hub 15 SP2 0.9.1-bp152.4.3.1
  • libmysofa openSUSE Leap 15.2 0.9.1-lp152.3.3.1

opensuse advisories openSUSE-SU-2021:0459-1openSUSE-SU-2021:0444-1

Is CVE-2019-16095 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-16095 updated cvss 7.5

libmysofa: invalid read in getDimension function in hrtf/reader.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.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

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.