dbcve.org
Jboss Application ServerApplication · Redhat

CVE-2013-3734

MEDIUM · 6.6 CVSS v3.0 Published 2017-10-24
Fix available
A fix is available. Upgrade to after 1.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 Embedded Jopr component in JBoss Application Server includes the cleartext datasource password in unspecified HTML responses, which might allow (1) man-in-the-middle attackers to obtain sensitive information by leveraging failure to use SSL or (2) attackers to obtain sensitive information by reading the HTML source code. NOTE: the vendor says that this does not cross a trust boundary and that it is recommended best-practice that SSL is configured for the administrative console

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

The Embedded Jopr administration/monitoring component in JBoss Application Server exposes datasource passwords in cleartext within HTML responses. This occurs when the admin console displays or includes password information without masking, allowing any user with access to the HTML response (either via MITM interception or by viewing page source) to retrieve the plaintext password.

MitigationEnable SSL/TLS for the JBoss administrative console and review all HTML response outputs from the Embedded Jopr component to ensure credentials are not being transmitted or displayed in plaintext. If the password exposure is in the application code itself, refactor to avoid sending sensitive data to frontend responses.

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:<= 1.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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed JBoss Application Server version
    Check the version file in the JBoss installation directory, typically found in version.properties or release notes, or run 'java -jar jbossas.jar' if present in the bin directory to display version information
    Affected if The installed version is JBoss AS 1.2 or earlier (1.0.x, 1.1.x, 1.2.x)
  2. Locate the Embedded Jopr component
    Search for jopr-related JAR files in the JBoss installation, typically under server/all/deploy or server/default/deploy directory, or check for 'embedded-jopr' in the lib or deploy directory structure
    Affected if The Embedded Jopr administration/monitoring component is deployed on the server
  3. Access the JBoss admin console and inspect HTML responses
    Navigate to the admin console URL (typically on port 8080 or 8443 under /admin-console or similar paths), then view the page source or intercept the HTTP response to examine if datasource password fields contain plaintext values instead of masked characters
    Affected if The HTML response contains plaintext passwords in form fields or displayed text related to datasource configurations
  4. Check for datasource configuration exposure
    Examine any datasource configuration pages within the admin console, specifically look for fields labeled 'password', 'Connection Password', or similar that display unmasked character data
    Affected if Datasource password fields show unmasked plaintext characters rather than password masking (dots or asterisks)
  5. Verify admin console access control
    Confirm whether the admin console is accessible over unencrypted HTTP (port 8080) versus encrypted HTTPS (port 8443), and check if network traffic between client and server could be intercepted
    Affected if Admin console is accessible over unencrypted HTTP or network traffic could be intercepted by unauthorized parties

You are affected if you are running JBoss Application Server 1.2 or earlier with the Embedded Jopr component deployed and the admin console exposes plaintext passwords in HTML 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 a release after 1.2
Interim mitigation

Enable SSL/TLS for the JBoss administrative console and review all HTML response outputs from the Embedded Jopr component to ensure credentials are not being transmitted or displayed in plaintext. If the password exposure is in the application code itself, refactor to avoid sending sensitive data to frontend responses.

Fix this in Jboss Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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