CVE-2020-6293
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 - 7.30, 7.31, 7.40, 7.50, allows an unauthenticated attacker to upload a malicious file and also to access, modify or make unavailable existing files but the impact is limited to the files themselves and is restricted by other policies such as access control lists and other upload file size restrictions, leading to Unrestricted File Upload.
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 confidenceUnrestricted File Upload vulnerability in SAP NetWeaver Knowledge Management versions 7.30-7.50 allows unauthenticated attackers to upload malicious files and access, modify, or make unavailable existing files. While impact is limited to the file system itself and constrained by ACLs and file size restrictions, the lack of authentication requirement and potential for malicious file storage poses a security risk.
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.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Identify SAP NetWeaver Knowledge Management versionUse SAP transaction code SM37 or execute 'sapcontrol -nr <instance> -function GetVersionInfo' to retrieve the installed version of the Knowledge Management component. Alternatively, check the SAP system information via SAP MII version details or SAP LMDB.Affected if The installed version matches 7.30, 7.31, 7.40, or 7.50 exactly.
-
Confirm Knowledge Management is deployed and runningExecute 'sapcontrol -nr <instance> -function GetProcessList' and look for processes related to Knowledge Management or check via SAP transaction code SMICM for the ICM web dispatcher status exposing KM endpoints.Affected if Knowledge Management is actively running and accessible.
-
Identify Knowledge Management upload endpointsReview the SAP ICM/ICF configuration via transaction code SICF. Look for KM-related service paths such as /sap/bc/km and /sap/bc/rest/api/knowledge management that handle file uploads.Affected if KM upload servlet paths are active in the ICF tree without authentication restrictions.
-
Review ACLs on KM upload directoriesAccess the KM Configuration iView via SAP Enterprise Portal or use transaction code FILE to inspect the file system paths configured for KM uploads (typically under /usr/sap/<SID>/<instance>/work or portal content directories). Verify ACL permissions allow unauthenticated write access.Affected if ACLs permit write access from unauthenticated or weakly authenticated contexts.
Your environment is affected if SAP NetWeaver Knowledge Management version 7.30, 7.31, 7.40, or 7.50 is installed with KM upload functionality exposed and permissive ACLs on upload directories.
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 SAP security patches when available. In the interim, enforce strict file type validation, review and tighten ACLs on Knowledge Management upload directories, and ensure file size restrictions are properly configured to limit exploitation.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6293 — 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-6293 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