Jboss Application ServerApplication · Redhat

CVE-2011-3606

MEDIUM · 5.4 CVSS v3.1 Published 2019-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A DOM based cross-site scripting flaw was found in the JBoss Application Server 7 before 7.1.0 Beta 1 administration console. A remote attacker could provide a specially-crafted web page and trick the valid JBoss AS user, with the administrator privilege, to visit it, which would lead into the DOM environment modification and arbitrary HTML or web script execution.

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

A DOM-based cross-site scripting (XSS) vulnerability in the JBoss Application Server 7 administration console before version 7.1.0 Beta 1 allows remote attackers to inject arbitrary HTML or JavaScript code through specially-crafted web pages that modify the DOM when visited by authenticated administrators.

MitigationUpgrade JBoss Application Server to version 7.1.0 Beta 1 or later to obtain the vendor patch. If immediate upgrading is not feasible, restrict administrative console access to trusted networks or VPN-only connections to reduce exposure.

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 Application ServerApplication
Affected:= 7.0.0= 7.0.1= 7.0.2

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Verify JBoss Application Server is installed
    Locate the JBoss installation directory and check for the presence of JBoss AS 7 components. Common paths include /opt/jboss-as or custom installation directories. Look for jboss-as-7.x folder structure.
    Affected if JBoss Application Server version 7.0.x is installed and running
  2. Determine the exact JBoss AS version
    Check the version file in the JBoss installation, typically found in the root jboss-as-7.x directory or through the startup logs. Look for version manifests or readme files indicating 7.0.0, 7.0.1, or 7.0.2.
    Affected if Installed version matches 7.0.0, 7.0.1, or 7.0.2 exactly
  3. Confirm admin console is accessible
    Verify the JBoss administration console web interface is enabled and reachable. The console typically runs on port 9990 or 8080 under the /admin or /console path. Check the standalone.xml or domain.xml configuration for console subsystem status.
    Affected if Administration console is enabled and network-accessible
  4. Check for authenticated administrator access
    Review logs and configuration to determine if any administrator accounts exist and have accessed the console. The XSS requires an authenticated administrator to visit a malicious page.
    Affected if Administrative users exist and have active or recent console sessions

You are affected if JBoss Application Server 7.0.0, 7.0.1, or 7.0.2 is running with the administration console enabled and administrator accounts are configured.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade JBoss Application Server to version 7.1.0 Beta 1 or later to obtain the vendor patch. If immediate upgrading is not feasible, restrict administrative console access to trusted networks or VPN-only connections to reduce exposure.

Fix this in Jboss Application Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3606 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-3606 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