CVE-2023-39327VulnerabilityPublished 13 Jul 2024Updated 21 Nov 2025

CVE-2023-39327: Uncontrolled Resource Consumption

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Monitor for and apply official OpenJPEG patches or updates addressing CVE-2023-39327 as soon as they become available. 2. Implement strict input validation and filtering to block suspicious or malformed JPEG 2000 images before processing. 3. Use resource limiting techniques such as CPU and memory quotas or timeouts on image decoding processes to prevent resource exhaustion. 4. Employ sandboxing or containerization for image processing components to isolate potential impacts. 5. Educate users and administrators about the risks of opening untrusted image files, especially from unknown sources. 6. Integrate security scanning tools that detect malformed images in file upload or ingestion workflows. 7. Review and update incident response plans to include scenarios involving denial-of-service caused by image processing vulnerabilities. 8. Consider alternative image processing libraries with active maintenance and security support if OpenJPEG updates are delayed.

Description

A flaw was found in OpenJPEG. Maliciously constructed pictures can cause the program to enter a large loop and continuously print warning messages on the terminal.

Impact

For European organizations, the primary impact is a potential denial-of-service condition when processing malicious JPEG 2000 images using OpenJPEG 2.5.0. This can disrupt services that rely on image decoding, such as digital media platforms, content management systems, and software development environments. The vulnerability does not expose sensitive data or allow unauthorized changes, so confidentiality and integrity impacts are negligible. However, availability degradation can affect business continuity, especially in industries with high volumes of image processing like publishing, healthcare imaging, and digital archiving. The requirement for user interaction limits remote exploitation but does not eliminate risk, as attackers could deliver malicious images via email attachments, downloads, or embedded content. The lack of known exploits reduces immediate threat but does not preclude future attacks. European organizations with automated image processing pipelines or user-facing applications that handle JPEG 2000 images should assess exposure and prepare mitigations to prevent service interruptions.

References

Community reviews

Loading reviews…