dbcve.org
Jboss Enterprise Application PlatformApplication · Redhat

CVE-2017-2595

MEDIUM · 6.5 CVSS v3.0 Published 2018-07-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
It was found that the log file viewer in Red Hat JBoss Enterprise Application 6 and 7 allows arbitrary file read to authenticated user via path traversal.

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

A path traversal vulnerability exists in the log file viewer component of Red Hat JBoss Enterprise Application Platform 6 and 7. An authenticated attacker can manipulate file path parameters using directory traversal sequences (e.g., '../') to read arbitrary files on the host system outside the intended log directory.

MitigationApply the appropriate Red Hat security patches for JBoss EAP 6 and 7. Prior to patching, restrict access to the administration console and log viewer to trusted users only, and implement network segmentation to limit exposure.

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.4.0= 7.0.0= 7.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
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. Identify installed JBoss EAP version
    Locate and examine the JBoss EAP installation to determine the exact version number (check version files in the installation directory or the admin console about section)
    Affected if The installed version matches 6.0.0, 6.4.0, 7.0.0, or 7.1.0 exactly
  2. Verify if administration console is accessible
    Check network accessibility of the JBoss administration console (typically ports 8080, 8443, or configured admin ports) and whether it requires authentication
    Affected if The administration console is reachable over the network without proper network restrictions
  3. Confirm log viewer component is enabled
    Determine if the web-based log file viewer functionality is available and enabled in the JBoss EAP installation
    Affected if The log viewer component is accessible through the administration interface or web console
  4. Check for external network exposure
    Review firewall rules and network configuration to determine if the management interfaces (including log viewer) are exposed to untrusted networks
    Affected if The JBoss management interfaces are accessible from outside the trusted network perimeter

You are affected if you are running JBoss EAP version 6.0.0, 6.4.0, 7.0.0, or 7.1.0 AND the log viewer component is accessible to authenticated users on the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate Red Hat security patches for JBoss EAP 6 and 7. Prior to patching, restrict access to the administration console and log viewer to trusted users only, and implement network segmentation to limit exposure.

Fix this in Jboss Enterprise Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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