Skip to content
Fencer Intel
high 8.8

CVE-2018-19541 json

An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17, 1.900.1…

published 7y ago modified 25d ago also EUVD-2018-11230

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

Summary

An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17, 1.900.18, 1.900.19, 1.900.20, 1.900.21, 1.900.22, 1.900.23, 1.900.24, 1.900.25, 1.900.26, 1.900.27, 1.900.28, 1.900.29, 1.900.30, 1.900.31, 2.0.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.10, 2.0.11, 2.0.12, 2.0.13, 2.0.14, 2.0.15, 2.0.16. There is a heap-based buffer over-read of size 8 in the function jas_image_depalettize in libjasper/base/jas_image.c.

Patch / fix

  • jasper SLES for SAP 12 SP4, SLES 12 SP4, SLED 12 SP4 +1 more 1.900.14-195.15.1
  • jasper SLE Module for Desktop Applications 15 SP1, SLE Module for Desktop Applications 15, SLE Module for Basesystem 15 SP1 +1 more 2.0.14-3.8.1

suse advisories SUSE-SU-2019:2513-1SUSE-SU-2019:2512-1

  • jasper openSUSE Tumbleweed 2.0.33-1.2
  • jasper openSUSE Leap 15.1 2.0.14-lp151.4.3.1
  • jasper openSUSE Leap 15.0 2.0.14-lp150.2.6.1

opensuse advisories openSUSE-SU-2024:10869-1openSUSE-SU-2019:2282-1openSUSE-SU-2019:2279-1

Is CVE-2018-19541 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-2018-19541 updated cvss 4.4

jasper: heap-based buffer over-read of size 8 in jas_image_depalettize in libjasper/base/jas_image.c

  • Red Hat Enterprise Linux 6 jasper, jasper-libs, jasper-utils
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 7 jasper, jasper-libs, jasper-utils Red Hat Enterprise Linux 8 jasper, jasper-libs, mingw-jasper, mingw32-jasper, mingw64-jasper
    affected: no fix available “Fix deferred”
  • Red Hat Enterprise Linux 5 netpbm
    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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
25d ago

Exploit prediction

2.80% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/mdadams/jasper/issues/182 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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