CVE-2020-6203
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 · uneditedSAP NetWeaver UDDI Server (Services Registry), versions- 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50; allows an attacker to exploit insufficient validation of path information provided by users, thus characters representing 'traverse to parent directory' are passed through to the file APIs, leading to Path Traversal.
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 confidenceSAP NetWeaver UDDI Server contains a path traversal vulnerability due to insufficient validation of path information. Attackers can use directory traversal sequences (e.g., '../') in user-supplied paths to access files outside the intended directory via file APIs.
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= 7.10= 7.11= 7.20= 7.30= 7.31= 7.40= 7.50CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP NetWeaver installation and versionRun the SAP kernel version command (e.g., 'sapcontrol -nr <instance> -function GetVersion' or check the kernel patch level via SM51). Compare the displayed NetWeaver version against the affected list: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, 7.50.Affected if The installed NetWeaver version matches any of these exact versions: 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50.
-
Confirm UDDI Server component is installedCheck the SAP system landscape using SAP Manager (SAINT) or via transaction SPAM/SAINT to list installed software components. Look for the UDDI Server component in the installed packages.Affected if The UDDI Server component appears in the installed SAP software components.
-
Verify UDDI Server is runningUse SAP transaction SM37 or the sapcontrol command (e.g., 'sapcontrol -nr <instance> -function GetProcessList') to check if the UDDI Server process (uddi_server) is running.Affected if The UDDI Server process is active and listening on its configured ports.
-
Check UDDI Server endpoint accessibilityAccess the UDDI Server web service endpoint (typically at /uddi/services or similar path under the SAP Web Dispatcher/ICM) using a browser or curl to confirm the service is reachable.Affected if The UDDI Server endpoint responds with a service WSDL or UDDI inquiry interface, indicating it is exposed.
You are affected if your SAP NetWeaver version is exactly 7.10, 7.11, 7.20, 7.30, 7.31, 7.40, or 7.50 AND the UDDI Server component is installed and running, exposing the path traversal-vulnerable file APIs.
Generated from the published advisory. Verify against your own configuration.
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 dataApply available SAP security patches. As a temporary workaround, implement input validation to reject path traversal characters and deploy a WAF rule to block requests containing '../' or similar sequences.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6203 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-6203 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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