Skip to content
Fencer Vulns
medium 5.5

CVE-2018-7731 json

An issue was discovered in Exempi through 2.4.4.

published 2018-03-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-19446

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

Summary

An issue was discovered in Exempi through 2.4.4. XMPFiles/source/FormatSupport/WEBP_Support.cpp does not check whether a bitstream has a NULL value, leading to a NULL pointer dereference in the WEBP::VP8XChunk class.

Patch / fix

  • exempi Debian 14, Debian 13, Debian 12 2.4.5-1

debian advisories DEBIAN-CVE-2018-7731

  • exempi openSUSE Tumbleweed 2.5.2-1.3

opensuse advisories openSUSE-SU-2024:10745-1

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-7731 updated cvss 3.3

exempi: NULL pointer dereference in XMPFiles/source/FormatSupport/WEBP_Support.cpp:WEBP::VP8XChunk allows for denial of service via crafted file

  • Red Hat Enterprise Linux 6 exempi Red Hat Enterprise Linux 7 exempi Red Hat Enterprise Linux 8 exempi
    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.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • bugs.freedesktop.org https://bugs.freedesktop.org/show_bug.cgi?id=105247 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/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 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.