Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-7061

EAP: Sensitive data can be exposed at the server level in domain mode

Overview

Published
10 Sep 2018
Modified
17 Jun 2026
Medium CVE
0 Registry packages
367 OS packages
1 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
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

Weakness: CWE-200

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 152 fixes

Red Hat 1 release · 136 packages

fixed 152
eap7-netty-xnio-transport eap7-apache-mime4j eap7-jboss-aesh eap7-mustache-java eap7-jboss-annotations-api-1-2-spec eap7-jboss-ejb-api-3-2-spec +130
Red Hat fixes for CVE-2016-7061
ReleasePackageFixed inAdvisory
7 eap7-netty-xnio-transport 0:0.1.2-1.Final_redhat_1.1.ep7.el7 RHSA-2017:3455
7 eap7-apache-mime4j 0:0.6.0-2.redhat_6.1.ep7.el7 RHSA-2017:3455
7 eap7-jboss-aesh 0:0.66.12-1.redhat_1.1.ep7.el7 RHSA-2017:0171
7 eap7-jboss-aesh 0:0.66.19-2.redhat_1.1.ep7.el7 RHSA-2017:3455
7 eap7-mustache-java +1 0:0.9.4-1.redhat_1.1.ep7.el7 RHSA-2017:3455
7 eap7-jboss-annotations-api-1-2-spec 0:1.0.0-2.Final_redhat_1.1.ep7.el7 RHSA-2017:3455

146 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.