CVE-2024-21011VulnerabilityPublished 17 Apr 2024Updated 30 Oct 2026

Red Hat Security Advisory: OpenJDK 17.0.11 Security Update for Portable Linux Builds

Affects Red Hat java-17-openjdkSource GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited : upgrade the Red Hat redhat/java-17-openjdk package to 17.0.11 when convenient.

Data as of 30 Oct 2026, 20:25 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 17.0.11

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Apr 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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 the Red Hat redhat/java-17-openjdk package to 17.0.11.

Affected software

Product	Affected	Fixed in
Red Hatredhat/java-17-openjdk`pkg:rpm/redhat/java-17-openjdk`Other threats	Affected <17.0.11	Fixed in 17.0.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the Red Hat OpenJDK 17 update to version 17.0.11 for portable Linux builds as provided in the Red Hat advisory RHSA-2024:1823. This update includes fixes for all listed vulnerabilities. Refer to Red Hat's official update instructions at https://access.redhat.com/articles/11258 for detailed guidance on applying the update. No additional mitigation steps are indicated by the vendor.

Description

Red Hat has released a security update for its OpenJDK 17 build for portable Linux, version 17.0.11, replacing version 17.0.10. This update addresses multiple vulnerabilities including a crash caused by long exception messages, an integer overflow in the C1 compiler, a compilation failure in the C2 compiler, and an improper reverse DNS lookup in the HTTP/2 client. These issues have been assigned CVE identifiers CVE-2024-21011, CVE-2024-21068, CVE-2024-21094, and CVE-2024-21012 respectively. The update is rated with moderate security impact by Red Hat. For remediation, users should apply the OpenJDK 17.0.11 update as per Red Hat's guidance.

Impact

The vulnerabilities fixed in this update can cause application crashes (CVE-2024-21011), incorrect compiler behavior due to integer overflow and compilation failures (CVE-2024-21068, CVE-2024-21094), and potential security issues related to improper reverse DNS lookups in the HTTP/2 client (CVE-2024-21012). These issues could affect the stability and security of Java applications running on the affected OpenJDK build. Red Hat classifies the overall impact as moderate.

CWE-117Improper Output Neutralization for Logs (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Logging (opens in a new tab)
Content Security Policy (opens in a new tab)
Application Logging Vocabulary (opens in a new tab)
OWASP ASVS 4.0.3
V7.3.1 (opens in a new tab)
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
Attack patterns
Audit Log Manipulation (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
Log Injection-Tampering-Forging (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-350Reliance on Reverse DNS Resolution for a Security-Critical Action (opens in a new tab)
Variant weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.
Architecture and Design
Use other means of identity verification that cannot be simply spoofed. Possibilities include a username/password or certificate.
Implementation
Perform proper forward and reverse DNS lookups to detect DNS spoofing.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V10.3.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
DNS Cache Poisoning (opens in a new tab)
DNS Rebinding (opens in a new tab)
User-Controlled Filename (opens in a new tab)
Pharming (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
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.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
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 30 Oct 2026, 19:41 UTC

WeaknessesCWE-117, CWE-350, CWE-190 +1

Technical details

References

Community reviews

Related threats