dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022. Known ransomware use
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2010-1428

HIGH · 7.5 CVSS v3.1 Published 2010-04-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Web Console (aka web-console) 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 obtain sensitive information via an unspecified request that uses a different method.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The JBoss Web Console performs access control checks only for GET and POST HTTP methods. Attackers can bypass authentication by using other HTTP methods (such as HEAD, OPTIONS, PUT, DELETE) to access sensitive administrative information without credentials.

MitigationUpgrade JBoss EAP to version 4.2.0.CP09 or 4.3.0.CP08 or later which includes the patched web-console. Alternatively, disable the web console if not required or restrict network access to the console via firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jboss Enterprise Application PlatformApplication
Affected:= 4.2.0= 4.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify JBoss EAP installation and version
    Locate the JBoss installation directory and check the version file (typically in $JBOSS_HOME/readme.txt or check jar manifest files in lib directory). Alternatively, run: java -jar $JBOSS_HOME/bin/jboss-version.jar or check server/release.info
    Affected if The installed version is 4.2.0.x before CP09 or 4.3.0.x before CP08 (including unpatched 4.2.0 or 4.3.0 base releases)
  2. Determine if Web Console is deployed
    Check for the presence of the web-console.war or jmx-console.war deployment in $JBOSS_HOME/server/all/deploy/ or the default deploy directory. Also check if these console URLs are accessible: http://localhost:8080/web-console/ or http://localhost:8080/jmx-console/
    Affected if The Web Console (web-console.war or jmx-console.war) is deployed and network-accessible
  3. Verify HTTP method handling configuration
    Review the WEB-INF/web.xml descriptor inside the deployed web-console.war (located at $JBOSS_HOME/server/all/deploy/http-invoker.sar/web-console.war/WEB-INF/web.xml or similar path) for security constraint definitions. Check if <http-method> elements are limited to only GET and POST
    Affected if The security constraint specifies only GET and POST methods (or omits method constraints entirely in a way that leaves other methods unrestricted)

If JBoss EAP version 4.2.0 through 4.2.0.CP08 or 4.3.0 through 4.3.0.CP07 is running with the Web Console deployed and accessible, the environment is vulnerable to authentication bypass via non-GET/POST HTTP methods.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JBoss EAP to version 4.2.0.CP09 or 4.3.0.CP08 or later which includes the patched web-console. Alternatively, disable the web console if not required or restrict network access to the console via firewall rules.

Recommended fix Moderate confidence

JBoss EAP 4.2.0.CP09 (for 4.2.x) or JBoss EAP 4.3.0.CP08 (for 4.3.x)

  1. Identify the current JBoss EAP version by checking the version string in the JBoss startup logs or the jbossas/version.properties file
  2. Download the appropriate patch from the Red Hat Customer Portal: JBoss EAP 4.2.0.CP09 for 4.2.x or JBoss EAP 4.3.0.CP08 for 4.3.x
  3. Stop the JBoss EAP instance gracefully
  4. Apply the patch following Red Hat's standard patch application process for CP (Critical Patch) updates
  5. Verify the patch was applied by checking the version shows 4.2.0.CP09 or 4.3.0.CP08
  6. Restart the JBoss EAP instance
  7. Test that the web console is accessible and that HTTP methods other than GET and POST are now properly restricted
Caveat These are patch updates with minimal risk; however, always test in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jboss Enterprise Application Platform Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-1428 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-1428 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data