dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-34320

CRITICAL · 9.3 CVSS v4.0 Published 2025-11-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
BASIS BBj versions prior to 25.00 contain a Jetty-served web endpoint that fails to properly validate or canonicalize input path segments. This allows unauthenticated directory traversal sequences to cause the server to read arbitrary system files accessible to the account running the service. Retrieved configuration artifacts may contain account credentials used for BBj Enterprise Manager; possession of these credentials enables administrative access and use of legitimate management functionality that can result in execution of system commands under the service account. Depending on the operating system and the privileges of the BBj service account, this issue may also allow access to other sensitive files on the host, including operating system or application data, potentially exposing additional confidential information.

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 Jetty web server component of BASIS BBj prior to version 25.00. The affected web endpoint fails to properly validate or canonicalize URL path segments, allowing unauthenticated attackers to use directory traversal sequences (e.g., ../../../) to access arbitrary files on the host system readable by the service account.

MitigationUpgrade BBj to version 25.00 or later to obtain the vendor patch. Until then, consider network segmentation, web application firewall rules to block traversal patterns, and restricting the service account's file system permissions to the minimum required.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 BBj installation and determine version
    Check the BBj installation directory for version information. Typical locations include the BASIS installation folder. Look for version manifests, about files, or use BBj command-line tools to query the installed version number.
    Affected if The installed version is any version prior to 25.00 (e.g., 24.x, 23.x, or earlier releases).
  2. Confirm Jetty web server component is in use
    Identify whether the BBj environment is running Jetty as its web server. Check for Jetty configuration files in the BBj installation, or look for processes running Jetty servers that are part of the BBj deployment.
    Affected if Jetty is actively serving web endpoints for this BBj installation, as the vulnerability exists specifically in Jetty-served endpoints.
  3. Verify web endpoints are network-accessible
    Determine if the Jetty web endpoints are exposed to network access. Check the Jetty configuration for listener bindings (e.g., host/port bindings) and whether the service is bound to external interfaces versus localhost only.
    Affected if Jetty web endpoints are bound to external network interfaces or otherwise accessible beyond localhost, allowing unauthenticated attackers to reach the vulnerable endpoints.

You are affected if your BBj installation version is below 25.00 AND Jetty web endpoints are accessible on your network, as this combination allows unauthenticated path traversal attacks.

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

Upgrade BBj to version 25.00 or later to obtain the vendor patch. Until then, consider network segmentation, web application firewall rules to block traversal patterns, and restricting the service account's file system permissions to the minimum required.

Recommended fix Moderate confidence

BBj 25.00

  1. Upgrade BASIS BBj to version 25.00 or later to resolve the path traversal vulnerability in the Jetty-served web endpoint

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-2025-34320 — 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-2025-34320 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