dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2017-12167

MEDIUM · 5.5 CVSS v3.0 Published 2018-07-26
Fix available
A fix is available. Upgrade to 7.0.9 or later.
See remediation →
57/100
Remediation priority · Elevated
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
It was found in EAP 7 before 7.0.9 that properties based files of the management and the application realm configuration that contain user to role mapping are world readable allowing access to users and roles information to all the users logged in to the system.

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 EAP 7 before 7.0.9, properties-based configuration files for the management and application realm that store user-to-role mappings are set with world-readable permissions. This allows any user authenticated to the system to read these files and obtain sensitive user credentials and role assignments.

MitigationApply EAP 7.0.9 or later which addresses this vulnerability, and verify that realm properties files have restrictive permissions (640 or stricter) rather than world-readable (644).

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.9= 7.1.0= 7.0.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/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
    Run the version command or check the product version file in the JBoss installation directory (such as 'jboss-cli.sh --version' or the version.txt in the installation root)
    Affected if The version is 7.0.0, 7.1.0, or any version before 7.0.9 (e.g., 7.0.1 through 7.0.8)
  2. Locate the management realm properties file
    Find the properties file that stores user-to-role mappings for the management realm (commonly named mgmt-users.properties or similar in the configuration directory)
    Affected if The file exists in the JBoss EAP configuration directory
  3. Locate the application realm properties file
    Find the properties file that stores user-to-role mappings for the application realm (commonly named application-users.properties or similar in the configuration directory)
    Affected if The file exists in the JBoss EAP configuration directory
  4. Check file permissions on management realm properties file
    Run 'ls -la' on the management realm properties file to view its permissions (e.g., 'ls -la mgmt-users.properties')
    Affected if The file permissions are 644, 655, or any setting that grants read access to 'others' (the last digit is 4 or higher)
  5. Check file permissions on application realm properties file
    Run 'ls -la' on the application realm properties file to view its permissions (e.g., 'ls -la application-users.properties')
    Affected if The file permissions are 644, 655, or any setting that grants read access to 'others' (the last digit is 4 or higher)

You are affected if your JBoss EAP version is 7.0.0, 7.1.0, or any version before 7.0.9 AND either the management or application realm properties files have world-readable permissions (644 or less restrictive).

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.9 or later
Fixed in 7.0.9
Interim mitigation

Apply EAP 7.0.9 or later which addresses this vulnerability, and verify that realm properties files have restrictive permissions (640 or stricter) rather than world-readable (644).

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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