CVE-2024-1233
Java vulnerability analysis and mitigation

Overview

A flaw was found in JwtValidator.resolvePublicKey in JBoss EAP, where the validator checks jku and sends a HTTP request. During this process, no whitelisting or other filtering behavior is performed on the destination URL address, which may result in a server-side request forgery (SSRF) vulnerability. The vulnerability was discovered in February 2024 and affects JBoss Enterprise Application Platform (Red Hat CVE).

Technical details

The vulnerability exists in the JwtValidator.resolvePublicKey component where the validator processes the jku (JSON Web Key Set URL) header in JWT tokens. When validating tokens, if the jku header is present, the system sends an HTTP request to the specified URL without proper URL filtering or whitelisting mechanisms. The vulnerability has been assigned a CVSS v3.1 base score of 7.3 (High severity) with the vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L (GitHub Advisory).

Impact

The SSRF vulnerability could allow attackers to make HTTP requests to arbitrary URLs through the affected system, potentially enabling unauthorized access to internal network resources and exposure of sensitive information. While the immediate impact might not directly compromise sensitive data or system integrity, it opens a pathway for attackers to discover and interact with internal services (Red Hat CVE).

Exploitability

The vulnerability requires an attacker to craft a malicious JWT token with a specially crafted jku header. The exploitation complexity is considered Low as it doesn't require special privileges or user interaction, though it does require some knowledge of JWT token manipulation (GitHub Advisory).

Mitigation and workarounds

A mitigation has been implemented requiring that the jku header in a token must exactly match one of the values from a configured string of allowed values, or token validation will fail. The allowed jku values can be specified using the wildfly.elytron.jwt.allowed.jku.values. system property. For example, to set allowed jku values for JwtRealm, use the wildfly.elytron.jwt.allowed.jku.values.JwtRealm system property with a space-separated list of allowed URLs (WildFly Commit).

Additional resources


SourceThis report was generated using AI

Related Java vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-76904CRITICAL9.8
  • Java logoJava
  • org.geotools.jdbc:gt-jdbc-postgis
NoYesAug 21, 2026
GHSA-mqjf-5f49-2fjhCRITICAL9.8
  • Java logoJava
  • org.geotools:gt-jdbc-postgis
NoYesAug 21, 2026
CVE-2026-54049HIGH8.7
  • Java logoJava
  • org.sakaiproject.conversations:sakai-conversations-impl
NoNoAug 24, 2026
CVE-2026-63202HIGH7.5
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesAug 20, 2026
CVE-2026-54050MEDIUM6.5
  • Java logoJava
  • org.sakaiproject.profile2:profile2-api
NoYesAug 24, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management