Skip to content
Fencer Intel
medium 5.5

CVE-2018-9055 json

JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_firstone in libjasper/jpc/jpc_math.c.

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

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

Summary

JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_firstone in libjasper/jpc/jpc_math.c.

Patch / fix

  • jasper SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 1.900.14-195.8.1

suse advisories SUSE-SU-2018:1424-1

  • jasper openSUSE Tumbleweed 2.0.33-1.2

opensuse advisories openSUSE-SU-2024:10869-1

  • jasper Arch Linux 2.0.16-1

arch linux advisories AVG-1060

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-9055 updated cvss 5.5

jasper: reachable assertion in jpc_firstone() in jpc_math.c

  • Red Hat Enterprise Linux 5 netpbm Red Hat Enterprise Linux 6 jasper, jasper-libs, jasper-utils Red Hat Enterprise Linux 7 jasper, jasper-libs, jasper-utils Red Hat Enterprise Linux 8 jasper, jasper-libs Red Hat Enterprise Virtualization 3 mingw-virt-viewer, mingw32-virt-viewer, mingw64-virt-viewer
    affected: no fix planned “Will not fix”

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.74% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/mdadams/jasper/issues/172 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 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.