dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-54453

HIGH · 7.5 CVSS v3.1 Published 2024-12-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue was discovered in Kurmi Provisioning Suite before 7.9.0.35, 7.10.x through 7.10.0.18, and 7.11.x through 7.11.0.15. A path traversal vulnerability in the DocServlet servlet allows remote attackers to retrieve any file from the Kurmi web application installation folder, e.g., files such as the obfuscated and/or compiled Kurmi source code.

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 in the DocServlet servlet of Kurmi Provisioning Suite allows remote unauthenticated attackers to retrieve arbitrary files from the web application installation folder using directory traversal sequences (e.g., ../../../'). The CVSS 7.5 score (AV:N/AC:L/PR:N) confirms network-exploitable, low-complexity attacks without credentials, leading to information disclosure including potential access to source code.

MitigationApply vendor patches (7.9.0.35+, 7.10.0.19+, 7.11.0.16+) to remediate the path traversal in DocServlet; additionally implement strict input validation and path sanitization to block traversal sequences before deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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.1/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. Identify DocServlet exposure
    Check if the DocServlet endpoint is accessible on your Kurmi Provisioning Suite web application. Common paths include /DocServlet or /servlet/DocServlet. Inspect your web server configuration or reverse proxy rules to confirm whether this servlet is exposed to network requests.
    Affected if DocServlet is reachable over the network without authentication
  2. Determine installed Kurmi version
    Locate the Kurmi Provisioning Suite installation directory and identify the installed version. Check for version files, about pages, or the management console for the current software version. Common locations include the installation root folder or the web application's WEB-INF/lib directory for JAR file version metadata.
    Affected if The installed version falls below the fixed releases (7.9.0.35, 7.10.0.19, or 7.11.0.16) or the version cannot be determined from the installation
  3. Verify network accessibility
    Confirm that the Kurmi web interface is accessible from network segments. Review firewall rules, network ACLs, and web server bind addresses to determine if the application accepts remote connections. The vulnerability is exploitable remotely without authentication.
    Affected if The application is accessible from untrusted network locations (AV:N condition)
  4. Check for traversal input filtering
    Inspect the DocServlet configuration and any web application firewall (WAF), reverse proxy rules, or input validation logic that may block directory traversal sequences such as '../' or '..\'. Review servlet filter configurations in web.xml or equivalent deployment descriptors.
    Affected if No input validation or path sanitization is in place to filter or block traversal sequences in requests to DocServlet

A user is affected if their Kurmi Provisioning Suite has an accessible DocServlet, runs a version below 7.9.0.35/7.10.0.19/7.11.0.16, is network-reachable, and lacks input validation to block traversal sequences in HTTP requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches (7.9.0.35+, 7.10.0.19+, 7.11.0.16+) to remediate the path traversal in DocServlet; additionally implement strict input validation and path sanitization to block traversal sequences before deployment.

Recommended fix High confidence

Minimum: 7.9.0.35 (7.9.x branch), 7.10.0.19 (7.10.x branch), or 7.11.0.16 (7.11.x branch)

  1. Identify the currently installed Kurmi Provisioning Suite version by checking the application or system documentation
  2. Determine which version branch (7.9.x, 7.10.x, or 7.11.x) is currently in use
  3. Download the appropriate fixed version from the Kurmi Software official source: upgrade to 7.9.0.35 or higher for 7.9.x branch, 7.10.0.19 or higher for 7.10.x branch, or 7.11.0.16 or higher for 7.11.x branch
  4. Review the upgrade documentation and release notes for any specific migration requirements
  5. Perform a backup of the current Kurmi installation and configuration
  6. Execute the upgrade procedure following Kurmi's standard upgrade process
  7. Verify the installation by checking the version number and testing the DocServlet functionality
  8. Confirm the path traversal vulnerability is resolved by attempting to access files outside the web application folder (or use official verification steps from Kurmi)
Caveat No breaking changes documented in the CVE description; standard upgrade testing recommended

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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