dbcve.org
HawtioApplication · Hawt

CVE-2017-2594

HIGH · 7.5 CVSS v3.0 Published 2018-05-08
Fix available
A fix is available. Upgrade to after 1.4.68 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
hawtio before versions 2.0-beta-1, 2.0-beta-2 2.0-m1, 2.0-m2, 2.0-m3, and 1.5 is vulnerable to a path traversal that leads to a NullPointerException with a full stacktrace. An attacker could use this flaw to gather undisclosed information from within hawtio's root.

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

Path traversal vulnerability in hawtio versions before 1.5 and 2.0-m3 allows attackers to craft malicious URL paths that cause a NullPointerException, exposing the full stack trace and revealing undisclosed files and directories within the application's root structure.

MitigationUpgrade hawtio to version 1.5 or later (or 2.0-m3/beta-1/beta-2), or apply the vendor-supplied patch to remediate the path traversal and prevent stack trace information disclosure.

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
HawtioApplication
Affected:<= 1.4.68

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

CVSS:3.0/AV:N/AC:L/PR:N/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. Locate the hawtio installation and identify its version
    Inspect the hawtio WAR file name, the pom.xml of the project, the MANIFEST.MF file inside the WAR, or the hawtio startup logs to find the version number
    Affected if The version cannot be determined or the version is earlier than 1.5.0
  2. Compare the installed version to the affected range
    Check if the identified version is 1.4.68 or earlier, or any version below 2.0-m3 that is not patched
    Affected if The installed hawtio version is 1.4.68 or lower
  3. Confirm the hawtio web console is accessible
    Verify that the hawtio HTTP endpoints are exposed and reachable on the network or locally (typically at /hawtio or /jolokia)
    Affected if The web console is exposed and the version is within the affected range

A user is affected if hawtio version 1.4.68 or earlier is deployed and the web interface is accessible, allowing crafted URL paths to trigger the path traversal and expose stack trace information.

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.4.68
Interim mitigation

Upgrade hawtio to version 1.5 or later (or 2.0-m3/beta-1/beta-2), or apply the vendor-supplied patch to remediate the path traversal and prevent stack trace information disclosure.

Fix this in Hawtio Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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