Skip to content
Noroxi
CVE-2018-20846· NVD / CVE Program· CNA mitre

Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 81.9% of all records.
  • Anyone who can reach it over the internet 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.
  • Fixed version: openjpeg2 (Debian:12) 2.3.1-1; openjpeg2 (SUSE:HPE Helion OpenStack 8) 2.1.0-4.15.1; openjpeg2 (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 2.3.0-150000.3.8.1.

Low priority for now. Upgrade to openjpeg2 (Debian:12) 2.3.1-1; openjpeg2 (SUSE:HPE Helion OpenStack 8) 2.1.0-4.15.1; openjpeg2 (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 2.3.0-150000.3.8.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Out-of-bounds accesses in the functions pi_next_lrcp, pi_next_rlcp, pi_next_rpcl, pi_next_pcrl, pi_next_rpcl, and pi_next_cprl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Jun 26, 2019
Updated
Jun 16, 2026
EPSS
2.1% · 81th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2018-20846

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
uclouvainopenjpeg

Affected versions

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

  • uclouvain openjpegup to 2.3.0 inclusive

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12openjpeg2before 2.3.1-12.3.1-1
SUSE:HPE Helion OpenStack 8openjpeg2before 2.1.0-4.15.12.1.0-4.15.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3openjpeg2before 2.3.0-150000.3.8.12.3.0-150000.3.8.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3openjpeg2before 2.3.0-150000.3.8.12.3.0-150000.3.8.1
SUSE:Linux Enterprise Module for Desktop Applications 15 SP3openjpegbefore 1.5.2-150000.4.10.11.5.2-150000.4.10.1
SUSE:Linux Enterprise Module for Desktop Applications 15 SP3openjpegbefore 1.5.2-150000.4.10.11.5.2-150000.4.10.1

Other highest-scoring records for the same primary product.

  • CVE-2012-3358Multiple heap-based buffer overflows in the j2k_read_sot function in j2k.c in OpenJPEG 1.5 allow remote attackers to cause a denial of servi
    42Plan
  • CVE-2017-17480In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the pgxtovolume function in jp3d/convert.c.
    41Plan
  • CVE-2013-4290Stack-based buffer overflow in OpenJPEG before 1.5.2 allows remote attackers to have unspecified impact via unknown vectors to (1) lib/openj
    41Plan
  • CVE-2013-4289Multiple integer overflows in lib/openjp3d/jp3d.c in OpenJPEG before 1.5.2 allow remote attackers to have unspecified impact and vectors, wh
    41Plan
  • CVE-2017-17479In OpenJPEG 2.3.0, a stack-based buffer overflow was discovered in the pgxtoimage function in jpwl/convert.c.
    40Plan
  • CVE-2018-7648An issue was discovered in mj2/opj_mj2_extract.c in OpenJPEG 2.3.0.
    39Monitor

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
debian:openjpeg22.3.1-1 · Debian:12Package registry (OSV)
opensuse:openjpeg1.5.2-150000.4.10.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:openjpeg22.3.0-150000.3.8.1 · openSUSE:Leap 15.3Package registry (OSV)
suse:openjpeg1.5.2-150000.4.10.1 · SUSE:Linux Enterprise Module for Desktop Applications 15 SP3Package registry (OSV)
suse:openjpeg22.1.0-4.15.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:openjpeg22.3.0-150000.3.8.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package 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

  • Anyone who can reach it over the internet 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
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

CVSS vector

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

nvd-primary

Change log

  1. Fix✗ → ✓

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

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records