Skip to main content
CVE-2024-21011VulnerabilityPublished Updated

SUSE · security update for java-17-openjdk

Affects SUSESource GCVE Database

0

Mentioned vulnerabilities

Not known to be exploited : upgrade to 9.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

Severity
Medium

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

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade SUSE to 9.0.

Affected software

ProductAffectedFixed in
SUSE Product Security Team SUSEAffected
  • >=8.4 <9.0
  • >=9.0
Fixed in
  • 9.0

AI-suggested

A security update for java-17-openjdk is available from Red Hat and should be applied promptly. All running instances of OpenJDK Java must be restarted after applying the update for the fixes to take effect. Refer to the Red Hat advisory RHSA-2024:1825 for detailed update instructions.

Description

Multiple moderate-impact security vulnerabilities have been identified and fixed in the java-17-openjdk packages for Red Hat Enterprise Linux. These include a crash caused by a long exception message, an integer overflow in the C1 compiler address generation, a compilation failure in the C2 compiler, and improper reverse DNS lookup in the HTTP/2 client. Users must apply the security update and restart all running OpenJDK Java instances to ensure the fixes take effect.

References

Community reviews

Loading reviews…