CVE-2020-6217
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 AS ABAP Business Server Pages Test Application IT00, versions 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, 754, does not sufficiently encode user-controlled inputs, resulting in reflected Cross-Site Scripting (XSS) vulnerability.
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 AS ABAP Business Server Pages (BSP) Test Application IT00 fails to properly encode user-controlled input, allowing attackers to inject malicious scripts via reflected parameters. This reflected XSS vulnerability enables session hijacking, credential theft, or defacement when users click crafted links.
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= 700= 701= 702= 730= 731= 740= 750= 751= 752= 753= 754CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 the SAP NetWeaver AS ABAP versionCheck the SAP system version using transaction SM51 or the SAP kernel version display. Compare the installed version against the affected list: 700, 701, 702, 730, 731, 740, 750, 751, 752, 753, 754.Affected if The installed version matches one of the listed versions.
-
Determine if BSP Test Application IT00 is deployedAccess the BSP application via its URL path, typically under /sap/bc/bsp/sap/it00/ or similar. Use transaction SE80 or SICF to list active BSP applications and check if IT00 is present and active.Affected if The BSP Test Application IT00 is found and accessible in the system.
-
Verify if the application accepts user-controlled URL parametersAccess the IT00 application with test parameters in the URL (for example, adding ?param=test to the application URL). Observe whether the parameter value is reflected back in the response without encoding.Affected if URL parameters are reflected in the HTML response without proper encoding.
-
Inspect browser response for unencoded script tagsSend a crafted URL with a script tag payload (for example, ?name=<script>alert(1)</script>) to the IT00 application and inspect whether the script tag executes or appears unescaped in the page source.Affected if The response contains the raw script tag or executes JavaScript, indicating the XSS vulnerability is present.
A system is affected if it runs any of the listed NetWeaver versions AND has the BSP Test Application IT00 deployed with user input reflected without encoding in the response.
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 proper output encoding to all user-controlled inputs in the BSP application, using context-appropriate encoding (HTML encoding for HTML body, URL encoding for URL parameters). Consider implementing a centralized encoding library or using SAP's built-in security features.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6217 — 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-6217 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