dbcve.org
Netweaver Application Server JavaApplication · Sap

CVE-2019-0345

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-14
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
A remote unauthenticated attacker can abuse a web service in SAP NetWeaver Application Server for Java (Administrator System Overview), versions 7.30, 7.31, 7.40, 7.50, by sending a specially crafted XML file and trick the application server into leaking authentication credentials for its own SAP Management console, resulting in Server-Side Request Forgery.

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 remote unauthenticated attacker can exploit a web service in SAP NetWeaver Application Server for Java (Administrator System Overview) by sending a specially crafted XML file. This SSRF vulnerability causes the application server to leak authentication credentials for its own SAP Management console, allowing the attacker to potentially access internal management interfaces.

MitigationApply SAP Security Note 2759091 (or subsequent relevant patches) to fix the XML handling in the Administrator System Overview component. If patches are unavailable, restrict access to the affected web service endpoint via network segmentation or web application firewall rules.

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
Netweaver Application Server JavaApplication
Affected:= 7.30= 7.31= 7.40= 7.50

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 SAP NetWeaver AS Java version
    Execute command 'sapcontrol -nr <instance_number> -function GetVersion' or check the SAP JVM version via 'java -version' and cross-reference with SAP PSAP* entries in system profile parameters (SAPSYSTEM, INSTANCE_NAME)
    Affected if Version equals 7.30, 7.31, 7.40, or 7.50 exactly as listed in affected versions
  2. Verify Administrator System Overview component is deployed
    Check for deployed web application in SAP NetWeaver Developer Studio or via SAP Management Console under Applications > Enterprise Applications for a package containing 'AdministratorSystemOverview' or similar naming
    Affected if The Administrator System Overview web application is found and running
  3. Confirm web service endpoint is accessible
    Attempt HTTP GET request to the ASO endpoint - typically under /webdynpro/resources/sap.com/tc~lm~itsam~admin~overview/ or similar SAP ITSAM paths, using curl or browser from an internal network location
    Affected if The endpoint responds with HTTP 200 and displays admin overview pages without authentication or with leaked credentials in response headers/body
  4. Check for credential leakage in XML responses
    Send a crafted XML payload to the web service endpoint and inspect response for SAP Management Console credentials (often in XML format or base64 encoded), monitor HTTP response headers and body for credential patterns
    Affected if Authentication credentials for the SAP Management console appear in the response after sending requests to the XML endpoint

You are affected if you run SAP NetWeaver AS Java versions 7.30, 7.31, 7.40, or 7.50 AND the Administrator System Overview web service is exposed, as the SSRF flaw will allow credential leakage via specially crafted XML 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP Security Note 2759091 (or subsequent relevant patches) to fix the XML handling in the Administrator System Overview component. If patches are unavailable, restrict access to the affected web service endpoint via network segmentation or web application firewall rules.

Fix this in Netweaver Application Server Java Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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