dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2013-6495

MEDIUM · 6.1 CVSS v3.1 Published 2019-12-11
Fix available
A fix is available. Upgrade to 6.1.0 / 6.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
JBossWeb Bayeux has reflected XSS

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 · moderate confidence

JBossWeb Bayeux protocol implementation contains a reflected cross-site scripting (XSS) vulnerability. The Bayeux endpoint (typically at /cometd or similar paths) reflects unsanitized user-supplied input back to the browser, allowing injection of malicious scripts.

MitigationApply the relevant JBoss patches or upgrade to a patched version. Additionally, implement input validation and output encoding on the Bayeux endpoint to prevent XSS.

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:>= 6.0.0, < 6.1.1
Jboss PortalApplication
Affected:>= 6.0.0, < 6.1.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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Check the installed JBoss version by inspecting the version file or startup logs. Common locations include $JBOSS_HOME/readme.txt or the startup banner output.
    Affected if The installed version is >= 6.0.0 and < 6.1.1 for JBoss EAP, or >= 6.0.0 and < 6.1.0 for JBoss Portal
  2. Locate Bayeux or CometD configuration
    Search the JBoss configuration files for Bayeux or CometD servlet mappings. Check web.xml, jboss-web.xml, or any context configuration files in the deployed applications for 'cometd' or 'bayeux' servlet definitions.
    Affected if A Bayeux or CometD servlet is configured and mapped to an endpoint path
  3. Identify the exposed Bayeux endpoint URL
    Review the servlet mapping in the configuration files to determine the URL path where the Bayeux endpoint is exposed. This is typically /cometd or similar paths as indicated in the deployment descriptor.
    Affected if The Bayeux endpoint is mapped to a publicly accessible URL path such as /cometd
  4. Verify the endpoint is reachable
    Attempt to access the configured Bayeux endpoint URL with a simple request to confirm it is exposed and responding. For example, send an HTTP GET request to http://<host>:<port>/<context>/cometd
    Affected if The endpoint responds to HTTP requests, indicating it is active and accessible
  5. Test for reflected input vulnerability
    Send a request to the Bayeux endpoint with a test payload in the query string or POST data, such as a simple script tag, and observe if the input is reflected back in the response without sanitization.
    Affected if User-supplied input is reflected verbatim in the response without encoding or validation

A user is affected if they are running a vulnerable JBoss version within the affected ranges AND have the Bayeux/CometD endpoint enabled and exposed, with unsanitized input being reflected in responses.

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
Upgrade available Upgrade to 6.1.0 / 6.1.1 or later
Fixed in 6.1.06.1.1
Interim mitigation

Apply the relevant JBoss patches or upgrade to a patched version. Additionally, implement input validation and output encoding on the Bayeux endpoint to prevent XSS.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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