Skip to content
Fencer Intel
medium 6.5

CVE-2018-20570 json

jp2_encode in jp2/jp2_enc.c in JasPer 2.0.14 has a heap-based buffer over-read.

published 7y ago modified 4mo ago also EUVD-2018-13124

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

Summary

jp2_encode in jp2/jp2_enc.c in JasPer 2.0.14 has a heap-based buffer over-read.

Patch / fix

  • jasper SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 1.900.14-195.22.1
  • jasper SLE Module for Package Hub 15 SP1, SLE Module for Desktop Applications 15 SP2, SLE Module for Desktop Applications 15 SP1 +2 more 2.0.14-3.16.1

suse advisories SUSE-SU-2020:2690-1SUSE-SU-2020:2689-1

  • jasper openSUSE Tumbleweed 2.0.33-1.2
  • jasper openSUSE Leap 15.2 2.0.14-lp152.7.3.1
  • jasper openSUSE Leap 15.1 2.0.14-lp151.4.9.1

opensuse advisories openSUSE-SU-2024:10869-1openSUSE-SU-2020:1523-1openSUSE-SU-2020:1517-1

Is CVE-2018-20570 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-20570 updated cvss 5.5

jasper: heap-based buffer over-read in jp2_encode()

  • Red Hat Enterprise Linux 5 netpbm Red Hat Enterprise Linux 6 jasper, jasper-libs, jasper-utils
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 jasper, jasper-libs, jasper-utils Red Hat Enterprise Linux 8 jasper, jasper-libs
    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

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

Exploits and checks

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