Skip to content
Fencer Intel
medium 6.5

CVE-2019-15757 json

libMirage 3.2.2 in CDemu has a NULL pointer dereference in the NRG parser in parser.c.

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

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

Summary

libMirage 3.2.2 in CDemu has a NULL pointer dereference in the NRG parser in parser.c.

Patch / fix

  • libmirage Package Hub 15 SP1, Package Hub 15 3.2.2-bp151.4.6.1
  • libmirage openSUSE Leap 15.1 3.2.2-lp151.3.6.1
  • libmirage openSUSE Leap 15.0 3.2.2-lp150.2.6.1

opensuse advisories openSUSE-SU-2019:2129-1openSUSE-SU-2019:2096-1openSUSE-SU-2019:2095-1

Is CVE-2019-15757 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-15757 updated cvss 6.2

libmirage: null pointer dereference in NGR parser in parser.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.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • gist.github.com https://gist.github.com/andreafioraldi/343d9ba64060b548c02362a5e61ec932 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/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.