dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2018-10934

MEDIUM · 5.4 CVSS v3.0 Published 2019-03-27
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 cross-site scripting (XSS) vulnerability was found in the JBoss Management Console versions before 7.1.6.CR1, 7.1.6.GA. Users with roles that can create objects in the application can exploit this to attack other privileged users.

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 stored cross-site scripting (XSS) vulnerability exists in JBoss Management Console versions prior to 7.1.6.CR1 and 7.1.6.GA. Authenticated users with object creation privileges can inject malicious JavaScript into console fields that executes in the browsers of other privileged users who view the crafted content.

MitigationUpgrade JBoss Management Console to version 7.1.6.CR1, 7.1.6.GA, or later. Until then, restrict object creation privileges to only trusted administrators and monitor 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 data
Jboss Enterprise Application PlatformApplication
Affected:= 7.0= 7.1.0
Single Sign OnApplication
Affected:= 7.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.0/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. Identify JBoss Management Console installation
    Access the JBoss Management Console web interface (typically at /console or /management) or check your JBoss EAP installation directory for the management console components
    Affected if The console is accessible and running on a JBoss EAP 7.0 or 7.1.0 installation
  2. Determine the installed JBoss EAP version
    Run the command 'jboss-cli.sh --version' or 'jboss-cli.bat --version' from the JBoss bin directory, or check the product.conf file in the JBoss installation
    Affected if The version is 7.0 or 7.1.0 (any patch level below 7.1.6.CR1 or 7.1.6.GA)
  3. Check console version directly
    If accessible, check the JBoss Management Console footer or about section for the console version number
    Affected if The console version is prior to 7.1.6.CR1 or 7.1.6.GA
  4. Verify network exposure of the console
    Check if the management console is exposed to untrusted networks by reviewing firewall rules, network configuration, or the standalone.xml/host.xml bindings for management interfaces
    Affected if The console is reachable from untrusted network segments without proper access controls
  5. Review user access privileges
    Check which authenticated users have object creation privileges in the management console by reviewing roles and permissions in the JBoss security realm configuration
    Affected if Users with object creation privileges exist and can create content that would be viewed by other administrators

You are affected if JBoss EAP 7.0 or 7.1.0 (or the Management Console prior to version 7.1.6.CR1/7.1.6.GA) is running and the console is accessible to authenticated users with object creation privileges.

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 Management Console to version 7.1.6.CR1, 7.1.6.GA, or later. Until then, restrict object creation privileges to only trusted administrators and monitor administrative actions.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10934 — 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-2018-10934 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