dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-42919

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Due to an Information Disclosure vulnerability in SAP NetWeaver Application Server Java, internal metadata files could be accessed via manipulated URLs. An unauthenticated attacker could exploit this vulnerability by inserting arbitrary path components in the request, allowing unauthorized access to sensitive application metadata. This results in a partial compromise of the confidentiality of the information without affecting the integrity or availability of the application server.

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

Information disclosure vulnerability in SAP NetWeaver Application Server Java where unauthenticated attackers can manipulate URLs by inserting arbitrary path components to gain unauthorized access to internal metadata files, resulting in partial confidentiality compromise.

MitigationApply available SAP security patches for this vulnerability and implement URL path validation controls to prevent arbitrary path component injection attacks.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 SAP NetWeaver AS Java installation
    Check for running processes containing 'sap' and 'jvm' or inspect installed SAP software via SAP Installer, SAP LM, or system inventory tools that enumerate SAP components
    Affected if Process or software listing shows SAP NetWeaver Application Server Java is present
  2. Determine SAP NetWeaver AS Java version
    Execute SAP command 'sapcontrol -nr <instance> -function GetVersion' or check version via SAP MMC, SAP NetWeaver Administrator, or version file in the SAP installation directory (e.g., /usr/sap/<SID>/<instance>/exe/sapjvm)
    Affected if Version cannot be determined or falls within the vulnerable version range for this CVE
  3. Verify HTTP(S) listener is exposed
    Check network configuration via SAP NetWeaver Administrator, SAP MMC, or netstat command for ports 5<instance>00-5<instance>99 (e.g., 50000) that SAP AS Java uses for HTTP/HTTPS
    Affected if SAP NetWeaver AS Java HTTP/HTTPS ports are reachable from network segments accessible to unauthenticated users
  4. Inspect HTTP access logs for suspicious URL patterns
    Review SAP AS Java access logs (located in /usr/sap/<SID>/<instance>/log or via transaction SLG1) for requests containing path traversal sequences such as '../', encoded equivalents, or unexpected path components leading to metadata files
    Affected if Logs contain URL manipulation attempts or successful unauthorized access to internal metadata files
  5. Check for unauthorized metadata file access
    Audit web container or dispatcher logs for requests to known internal metadata paths (e.g., /sap/monitoring/, /sap/metadata/, or similar internal endpoints) that should not be accessible to unauthenticated users
    Affected if Evidence exists of successful or attempted access to internal metadata files by unauthenticated sources

System is affected if SAP NetWeaver Application Server Java is running with an affected version and its HTTP/HTTPS interface is accessible to unauthenticated attackers who could exploit URL path manipulation to access internal metadata files.

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 available SAP security patches for this vulnerability and implement URL path validation controls to prevent arbitrary path component injection attacks.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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