dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2016-7061

MEDIUM · 6.5 CVSS v3.0 Published 2018-09-10
Fix available
A fix is available. Upgrade to 7.0.4 or later.
See remediation →
71/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
An information disclosure vulnerability was found in JBoss Enterprise Application Platform before 7.0.4. It was discovered that when configuring RBAC and marking information as sensitive, users with a Monitor role are able to view the sensitive information.

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

In JBoss Enterprise Application Platform before 7.0.4, the RBAC (Role-Based Access Control) implementation contains an information disclosure vulnerability where users assigned the Monitor role can view sensitive information that should be protected from their view. This represents an authorization bypass where the Monitor role incorrectly inherits access to sensitive resources.

MitigationUpgrade JBoss Enterprise Application Platform to version 7.0.4 or later to obtain the patch. After upgrading, verify that Monitor role users can no longer access sensitive information marked for protection under RBAC.

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.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check installed JBoss EAP version
    Use the management console or run 'jboss-cli.sh' with the command 'version' to retrieve the installed EAP version. Alternatively, check the manifest file in the installation directory.
    Affected if The installed version is any release prior to 7.0.4 (for example, 7.0.0, 7.0.1, 7.0.2, 7.0.3, or 7.0.3.GA).
  2. Verify RBAC is enabled
    Access the management console or use jboss-cli.sh to check the RBAC configuration. Run: '/core-service=management/access=authorization/role-mapping=Monitor' or inspect the security realm configuration.
    Affected if RBAC is enabled and the Monitor role is defined in the role mapping configuration.
  3. Confirm Monitor role users exist
    List users assigned the Monitor role by querying the role mapping or checking the users properties file referenced by the security realm.
    Affected if One or more users are assigned to the Monitor role.
  4. Identify sensitive resources accessible to Monitor role
    Review the management interface permissions for the Monitor role. Check which resources are readable by examining the attribute permissions under /core-service=management/access=authorization or through the web console's Role Definition view.
    Affected if The Monitor role has read access to sensitive resources (such as credential data, security realms, or system properties) that should be restricted.

You are affected if JBoss EAP version is before 7.0.4, RBAC is enabled with Monitor role users, and those Monitor users can access sensitive resources they should not be able to view.

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 7.0.4 or later
Fixed in 7.0.4
Interim mitigation

Upgrade JBoss Enterprise Application Platform to version 7.0.4 or later to obtain the patch. After upgrading, verify that Monitor role users can no longer access sensitive information marked for protection under RBAC.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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