CVE-2024-21131VulnerabilityPublished 17 Jul 2024Updated 11 Oct 2026

SUSE · security update for java-17-openjdk

Affects SUSESource GCVE Database

Mentioned vulnerabilities

Not known to be exploited : upgrade to 10.0 or 9.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.0, 9.0

Exploitation evidence

Disclosed: evidence found.
CVE published 17 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 2026-10-25.

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

Upgrade SUSE to 10.0 or 9.0.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=8.4 <9.0 >=9.0 <10.0 =1:17.0.12.0.7-2.el9.x86_64	Fixed in 9.0 10.0

AI-suggested

A security update for java-17-openjdk is available from Red Hat and SUSE. Users should apply the update promptly to remediate the vulnerabilities. After applying the update, all running OpenJDK Java instances must be restarted for the fixes to take effect. Refer to the vendor advisory at https://access.redhat.com/errata/RHSA-2024:4568 and https://access.redhat.com/articles/11258 for detailed update instructions.

Description

Multiple security vulnerabilities have been identified and fixed in the java-17-openjdk packages, which provide the OpenJDK 17 Java Runtime Environment and Software Development Kit. These include array index overflow, potential UTF8 size overflow, infinite loop due to excessive symbol length, pre-loop limit overflow, and out-of-bounds access in 2D image handling. The update addresses these issues to prevent potential security risks. The vulnerabilities affect various Red Hat Enterprise Linux and SUSE versions. A security update is available and should be applied, with a restart of all running OpenJDK Java instances required for the update to take effect.

Impact

The vulnerabilities could lead to issues such as array index overflows, size overflows, infinite loops, pre-loop limit overflows, and out-of-bounds memory access within the OpenJDK 17 runtime and SDK. These issues may cause application crashes or potentially be leveraged for further security exploits. The Red Hat advisory rates the security impact as Important, indicating a high severity level but does not provide specific CVSS scores. No known exploits in the wild have been reported at this time.

CWE-835Loop with Unreachable Exit Condition ('Infinite Loop') (opens in a new tab)
Base weakness
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:34 UTC

WeaknessesCWE-835, CWE-787

Technical details

References

Community reviews

Related threats