CVE-2013-6820
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 · uneditedUnrestricted file upload vulnerability in the SAP NetWeaver Development Infrastructure (NWDI) allows remote attackers to execute arbitrary code by uploading a file with an executable extension via unspecified vectors.
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 confidenceUnrestricted file upload vulnerability in SAP NetWeaver Development Infrastructure (NWDI) allows remote attackers to upload files with executable extensions, enabling arbitrary code execution. The high CVSS score of 9.3 reflects the critical nature of remote code execution in a potentially internet-facing enterprise component.
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 dataall versionsCVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 NWDI installationCheck for SAP NetWeaver Development Infrastructure components in the system: look for NWDI-related services, directories (typically under /usr/sap/<SID>/<instance>/j2ee/ or Windows equivalent), or process names containing 'NWDI' or 'jc00'/'jstart' in SAP contexts. Query SAP LMDB or use SAP's OS-level tools like sapcontrol -list if available.Affected if SAP NetWeaver Development Infrastructure is installed and running in the environment.
-
Verify NWDI file upload capability is enabledExamine the NWDI configuration files, specifically the DMS (Document Management System) configuration under the NWDI deployment: check configuration files in the NWDI cluster or in the j2ee/engine/config directory for upload-related settings. Look for properties enabling web-based file upload or the Design Time Repository (DTR) upload endpoints.Affected if The NWDI file upload or DTR web interface is accessible and not explicitly disabled in configuration.
-
Inspect NWDI upload directoriesLocate the NWDI upload directories - typically these are under the DTR or CMS workspace directories (search for paths like /DTR/, /repository/, or configured upload paths in NWDI config). List all files in these directories and check for unexpected executable extensions (.jsp, .exe, .bat, .sh, .ear, .war, .jar).Affected if Files with executable extensions (.jsp, .ear, .war, .exe, .bat, .sh) are present in NWDI upload directories.
-
Check NWDI network exposureReview network accessibility of NWDI web interfaces (port typically 50000-50010 range or custom SAP ports). Query firewall rules, load balancer configurations, or SAP ICM/Internet Communication Manager settings to determine if NWDI ports are exposed to untrusted or internet-facing networks.Affected if NWDI services are reachable from untrusted networks or directly from the internet.
If SAP NetWeaver Development Infrastructure is installed and its file upload functionality is accessible (enabled and network-exposed), the environment is affected by CVE-2013-6820.
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.
dbcve · scopedImmediately restrict or disable file upload functionality in NWDI to prevent executable file types. Apply SAP security patches for CVE-2013-6820 and limit network exposure of NWDI services to trusted internal networks only.
Apply SAP Security Note 1887912 for your specific NetWeaver SPS version; for newer environments, upgrade to a NetWeaver version that includes this security fix in its base release
- Check the SAP Support Portal for Security Note 1887912 which addresses this vulnerability
- Review the security note for specific patch/instructions applicable to your NetWeaver version and Support Package Stack (SPS)
- Apply the recommended security patch or implement the configuration changes specified in the note
- After patching, verify that file upload functionality in NWDI no longer accepts executable file extensions (.jsp, .exe, .bat, .sh, etc.)
- Test the remediation to ensure legitimate development files can be uploaded while executable extensions are blocked
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2013-6820 — 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-2013-6820 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