CVE-2020-6225
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 (Knowledge Management), versions (KMC-CM - 7.00, 7.01, 7.02, 7.30, 7.31, 7.40, 7.50 and KMC-WPC 7.30, 7.31, 7.40, 7.50), does not sufficiently validate path information provided by users, thus characters representing traverse to parent directory are passed through to the file APIs, allowing the attacker to overwrite, delete, or corrupt arbitrary files on the remote server, 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 Knowledge Management (KMC-CM and KMC-WPC) versions 7.00-7.50 contains a path traversal vulnerability where insufficient validation of user-supplied path information allows directory traversal characters to pass through to file system APIs. Attackers can exploit this to overwrite, delete, or corrupt arbitrary files on the server.
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.00= 7.01= 7.02= 7.30= 7.31= 7.40= 7.50= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Knowledge Management component installationCheck if SAP NetWeaver Knowledge Management (KMC-CM or KMC-WPC) components are installed on the system by reviewing the SAP system landscape directory or using transaction SM37 to list running KMC processesAffected if KMC-CM or KMC-WPC components are present on the system
-
Determine KMC-CM versionCheck the installed version of KMC-CM by reviewing SAP system information via transaction SM51 or by querying the SAP system landscape directory for component 'KM-CMC' versionAffected if Version equals 7.00, 7.01, 7.02, 7.30, 7.31, 7.40, or 7.50
-
Determine KMC-WPC versionCheck the installed version of KMC-WPC by reviewing SAP system information via transaction SM51 or by querying the SAP system landscape directory for component 'KM-WPC' versionAffected if Version equals 7.30, 7.31, 7.40, or 7.50
-
Verify web access to Knowledge ManagementCheck if the Knowledge Management URLs (typically under /sap/bc/km or /sap/portal/km) are accessible from the network by testing HTTP/HTTPS endpointsAffected if KMC web endpoints are reachable from untrusted networks without authentication controls
-
Review KMC configuration for traversal protectionInspect the Knowledge Management configuration files (km-config.xml or similar) in the SAP system to verify if input validation for path parameters is implementedAffected if Path traversal characters (.., /, \) are not being filtered or validated in KMC configurations
A system is affected if it runs KMC-CM versions 7.00-7.50 or KMC-WPC versions 7.30-7.50 AND the Knowledge Management component is web-accessible with insufficient path input validation.
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 the relevant SAP security patches for CVE-2020-6225 and implement strict input validation on path parameters within the Knowledge Management component to block traversal sequences.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6225 — 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-6225 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