CVE-2018-19540: 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

This week

HIGH 8.8WATCHLISTDOWNGRADEMITIGATEMITIGATE

CVE-2018-19540 is a high-severity flaw (CVSS 8.8) affecting jasper, linux enterprise desktop, linux enterprise server. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 overflow of size 1 in t

Why this priority

High severity
Public exploit reference
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	2.3% (top 17%)
CISA exploited list	No
Weakness	CWE-787
Published	2018-11-26
Last modified	2026-10-15

Publisher (CNA): MITRE · Vendor: debian · jasper project · suse

Last updated 2026-10-15 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-11-26 03:29 UTCPublished CVE record published
2026-10-15 18:17 UTCUpdated Record last modified

jasper project jasper DOWNGRADE

Affected: 2.0.14

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.14

1. Check installed version

apt-cache policy jasper || rpm -q jasper || jasper --version

2. No fixed release: DOWNGRADE to a release before 2.0.14 (Debian / Ubuntu)

apt-cache madison jasper sudo apt install jasper=<VERSION_BEFORE_2.0.14> sudo apt-mark hold jasper

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jasper sudo dnf downgrade jasper-<VERSION_BEFORE_2.0.14> sudo dnf versionlock add jasper

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

suse linux enterprise desktop MITIGATE

Affected: 12 sp3 · 12 sp4

Fixed in: no fixed release known

Safe to downgrade to: a release before 12

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

suse linux enterprise server MITIGATE

Affected: 11 sp3 · 11 sp4 · 12 sp1 · 12 sp2

Fixed in: no fixed release known

Safe to downgrade to: a release before 11

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

debian debian linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-19540?

jasper: downgrade or apply the listed mitigation; linux enterprise desktop: mitigate or apply the listed mitigation; linux enterprise server: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-19540 being exploited?

CVE-2018-19540 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-19540 affect?

CVE-2018-19540 affects jasper, linux enterprise desktop, linux enterprise server. Severity is high (CVSS 8.8). 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

How urgent is CVE-2018-19540?

Priority 62/100. High severity; Public exploit reference; On your watchlist

Software pages

Debian vulnerabilities

Related CVEs

CVE-2018-19543 HIGH 7.8 DOWNGRADE MITIGATE An issue was discovered in JasPer 2.0.14
CVE-2018-19542 MEDIUM 6.5 DOWNGRADE MITIGATE An issue was discovered in JasPer 2.0.14
CVE-2018-19541 HIGH 8.8 DOWNGRADE MITIGATE 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
CVE-2018-19539 MEDIUM 6.5 DOWNGRADE MITIGATE An issue was discovered in JasPer 2.0.14
CVE-2018-19139 MEDIUM 5.5 DOWNGRADE MITIGATE An issue has been found in JasPer 2.0.14

References

← Back to latest CVEs