Threats / Red Hat / CVE-2010-0738
CVE-2010-0738
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Red Hat JBoss vulnerability
JBoss JMX-Console fails to enforce access control for HTTP methods other than GET and POST, allowing remote attackers to bypass authentication and access the console.
Verdict
Today item, not a backlog item.
Remote attackers can circumvent access controls on the JMX-Console by using HTTP methods such as PUT, DELETE, or HEAD to reach protected functionality. This enables unauthorized administrative access to JBoss application servers without credentials.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
11 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-05-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.79415 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Red Hat, JBoss. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-264 Permissions/Privileges/Access Control — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft an HTTP request using a method like PUT or DELETE instead of GET/POST to reach the JMX-Console endpoint.
Business
Attackers gain unauthenticated access to critical JBoss management interfaces, enabling full system compromise.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I exploit this access to deploy malicious applications, modify configurations, or execute arbitrary code on the server.
Business
Enterprise applications running on affected JBoss instances face data theft, service disruption, and operational takeover.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistence by creating backdoor accounts or deploying ransomware payloads across the infrastructure.
Business
Organizations suffer ransomware infections, extended downtime, and potential extortion demands affecting business continuity.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05