Skip to content
Noroxi
CVE-2016-9583· NVD / CVE Program· CNA redhat

An out-of-bounds heap read vulnerability was found in the jpc_pi_nextpcrl() function of jasper before 2.0.6 when processing crafted input.

HighCVSS 7.8 · v3.0—No exploit Fix available
Published
Aug 1, 2018
Updated
Jun 16, 2026
EPSS
1.9% · 79th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.9%

CNA vs NVD score

NVD
7.8
CNA · redhat
5.5
2.3 point gap

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
redhatenterprise linux desktop
redhatenterprise linux server
redhatenterprise linux server aus
redhatenterprise linux server eus
redhatenterprise linux server tus
redhatenterprise linux workstation
jasper projectjasper
oracleoutside in technology

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • jasper project jasperbefore 2.0.6
  • oracle outside in technology8.5.3
  • redhat enterprise linux desktop6.0
  • redhat enterprise linux desktop7.0
  • redhat enterprise linux server6.0
  • redhat enterprise linux server7.0
  • redhat enterprise linux server aus7.3
  • redhat enterprise linux server aus7.4
  • redhat enterprise linux server aus7.6
  • redhat enterprise linux server eus7.3
  • redhat enterprise linux server eus7.4
  • redhat enterprise linux server eus7.5
  • redhat enterprise linux server eus7.6
  • redhat enterprise linux server tus7.3
  • redhat enterprise linux server tus7.6
  • redhat enterprise linux workstation6.0
  • redhat enterprise linux workstation7.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • The Jasper Project jasper

    • 2.0.6affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Tumbleweedjasperbefore 2.0.33-1.22.0.33-1.2
SUSE:Linux Enterprise Desktop 12 SP1jasperbefore 1.900.14-194.11.900.14-194.1
SUSE:Linux Enterprise Software Development Kit 11 SP4jasperbefore 1.900.14-134.32.11.900.14-134.32.1

Other highest-scoring records for the same primary product.

  • CVE-2017-5375JIT code allocation can allow for a bypass of ASLR and DEP protections leading to potential memory corruption attacks.
    49Plan
  • CVE-2018-14649It was found that ceph-isci-cli package as shipped by Red Hat Ceph Storage 2 and 3 is using python-werkzeug in debug shell mode.
    43Plan
  • CVE-2016-7050SerializableProvider in RESTEasy in Red Hat Enterprise Linux Desktop 7, Red Hat Enterprise Linux HPC Node 7, Red Hat Enterprise Linux Server
    41Plan
  • CVE-2010-5325Heap-based buffer overflow in the unhtmlify function in foomatic-rip in foomatic-filters before 4.0.6 allows remote attackers to cause a den
    41Plan
  • CVE-2018-5156A vulnerability can occur when capturing a media stream when the media source type is changed as the capture is occurring.
    40Plan
  • CVE-2018-12378A use-after-free vulnerability can occur when an IndexedDB index is deleted while still in use by JavaScript code that is providing payload
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:jasper2.0.33-1.2 · openSUSE:TumbleweedPackage registry (OSV)
suse:jasper1.900.14-134.32.1 · SUSE:Linux Enterprise Software Development Kit 11 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records