Cyber Resilience

CVE-2010-0738

Redhat Jboss Enterprise Application Platform 4.2.0 … 4.3.0

CISA KEVActive ExploitationEUVD ExploitedPublic PoCRansomware-linked
Published
28 April 2010
Modified
22 April 2026
KEV Added
25 May 2022
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.79 99.6th percentile
Risk Priority 80 floored blend · peak EPSS

Summary

CVE-2010-0738 is a medium-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Redhat Jboss Enterprise Application Platform. Its CVSS base score is 5.3 (Medium).

Operationally, ranked in the top 0.4% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

The JMX-Console web application in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before 4.2.0.CP09 and 4.3 before 4.3.0.CP08 performs access control only for the GET and POST methods, which allows remote attackers to…

more

send requests to this application's GET handler by using a different method.

CWE(s)
NVD-CWE-noinfoCWE-749
KEV Date Added
25 May 2022

Related Threats

Threat-Actor AttributionAI

Threat Group-3390 (G0027)
Newly discovered Chinese hacking group hacked 100+ websites to use as “watering holes” - Ars Technica

Likely ATT&CK TechniquesAI

Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.

T1190 Exploit Public-Facing Application Initial Accessconfidence: HIGH
The CVE describes a flaw in a web application that allows remote attackers to bypass access controls by using HTTP methods other than GET/POST, directly enabling exploitation of a public-facing application.
attack.mitre.org →
inferred from description + CWE + attributed actor TTPs (Threat Group-3390) · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2010-1428Same product: Redhat Jboss Enterprise Application Platformboth on KEV
CVE-2017-12149Same product: Redhat Jboss Enterprise Application Platformboth on KEV
CVE-2025-23367Same product: Redhat Jboss Enterprise Application Platform
CVE-2018-14667Same vendor: Redhatboth on KEV
CVE-2023-3171Same product: Redhat Jboss Enterprise Application Platform
CVE-2024-10234Same product: Redhat Jboss Enterprise Application Platform
CVE-2023-4503Same product: Redhat Jboss Enterprise Application Platform
CVE-2025-23368Same product: Redhat Jboss Enterprise Application Platform
CVE-2023-4061Same product: Redhat Jboss Enterprise Application Platform
CVE-2023-5379Same product: Redhat Jboss Enterprise Application Platform

Affected Assets

redhat
jboss enterprise application platform
4.2.0, 4.3.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 4 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V8.2.1

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

CM-7 Least Functionality
addresses: CWE-749

Explicitly prohibiting dangerous or unnecessary functions and services prevents exposure of methods that could be directly exploited.

SC-25 Thin Nodes
addresses: CWE-749

Minimal functionality removes or avoids exposure of dangerous methods and functions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 full match
prevents

Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.

PR.PS-06 mostly match
prevents

Secure SDLC practices stop developers from exposing dangerous functions in the first place.

ID.RA-01 partial match
prevents

Vulnerability identification processes will surface exposed dangerous methods during assessment.

PR.IR-01 partial match
prevents

Logical access controls at the network/environment layer can limit reachability of exposed functions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.

A.8.18 Use of privileged utility programs partial match
degrades

Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.

A.8.2 Privileged access rights partial match
prevents

Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle requires removal or protection of dangerous APIs during design and coding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate that dangerous methods are not exposed in interfaces.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.

References