CVE-2007-1157
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 · uneditedCross-site request forgery (CSRF) vulnerability in jmx-console/HtmlAdaptor in JBoss allows remote attackers to perform privileged actions as administrators via certain MBean operations, a different vulnerability than CVE-2006-3733.
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 confidenceCross-site request forgery (CSRF) vulnerability in JBoss jmx-console's HtmlAdaptor allows remote attackers to trick authenticated administrators into unknowingly executing privileged MBean operations. The attacker crafts malicious requests that the browser of an authenticated administrator automatically sends to the vulnerable jmx-console, enabling unauthorized administrative actions.
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 dataall versionsCVSS 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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Verify jmx-console is deployed and accessibleCheck for the presence of the jmx-console.war deployment in the JBoss deployment directory (e.g., $JBOSS_HOME/server/all/deploy/jmx-console.war or equivalent) and attempt to access http://<host>:8080/jmx-console/Affected if The jmx-console.war is deployed and responds to HTTP requests
-
Confirm HtmlAdaptor is enabledAccess the HtmlAdaptor endpoint directly at http://<host>:8080/jmx-console/HtmlAdaptor/ and verify it returns the adapter page rather than a 404 errorAffected if The HtmlAdaptor servlet responds and displays the MBean invocation interface
-
Check if jmx-console requires authenticationInspect the web.xml file located in jmx-console.war/WEB-INF/web.xml to determine if security constraints are configured for the HtmlAdaptor or the entire consoleAffected if No security-constraint is defined, or authentication is not enforced for the HtmlAdaptor URLs
-
Assess network exposure of the jmx-consoleReview network bind addresses in JBoss configuration files (e.g., jboss-service.xml, server.xml) and determine if the HTTP connector is bound to 0.0.0.0 or a publicly accessible IP addressAffected if The jmx-console is bound to a reachable network interface and accessible from untrusted networks
The environment is affected if the jmx-console HtmlAdaptor is deployed, enabled, and accessible with or without authentication enforcement.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataDisable or restrict access to the jmx-console/HtmlAdaptor if unused; otherwise apply vendor patches and implement anti-CSRF protections such as token-based validation for state-changing MBean operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1157 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-1157 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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