dbcve.org
Netweaver As Abap Business Server PagesApplication · Sap

CVE-2020-6229

MEDIUM · 6.1 CVSS v3.1 Published 2020-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
SAP NetWeaver AS ABAP (Business Server Pages application CRM_BSP_FRAME), versions 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 752, 75A, 75B, 75C, 75D, 75E, 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 confidence

SAP NetWeaver AS ABAP Business Server Pages application CRM_BSP_FRAME does not sufficiently encode user-controlled inputs, resulting in a reflected Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious scripts through unsanitized parameters that are reflected back to users in the application response.

MitigationApply SAP security patches for CVE-2020-6229 and implement proper output encoding for user-controlled inputs in the CRM_BSP_FRAME BSP application.

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
Netweaver As Abap Business Server PagesApplication
Affected:= 75a= 75b= 75c= 75d= 75e= 700= 701= 702= 710= 711= 730= 731

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed SAP NetWeaver AS ABAP version
    Execute transaction SM37 or use SAP MII version checker to determine the NetWeaver AS ABAP version. Check system info via SAP transaction code 'SM51' or review the SAP system profile parameters.
    Affected if Installed version matches one of: 75a, 75b, 75c, 75d, 75e, 700, 701, 702, 710, 711, 730, or 731.
  2. Verify CRM_BSP_FRAME BSP application is deployed
    Check for the existence of the CRM_BSP_FRAME BSP application in the SAP BSP repository. Use transaction SE80 or SE61 to browse BSP applications and search for 'CRM_BSP_FRAME'. Review BSP application metadata in table BSP 应用.
  3. Inspect HTTP request parameters for lack of encoding
    Capture an HTTP request to the CRM_BSP_FRAME application using transaction SM37 or a web proxy. Review how parameters are reflected in the response without proper HTML encoding.
    Affected if User-supplied parameters in the request are reflected in the response without encoding (visible as raw HTML/script tags rather than escaped entities).
  4. Review BSP application code for input validation
    Use transaction SE80 to open the CRM_BSP_FRAME BSP application. Inspect the controller and view files for presence of proper HTML encoding functions (such as HTML_ESCAPE or equivalent).
    Affected if Code lacks proper output encoding functions for user-controlled parameters before reflection.
  5. Check for suspicious injection patterns in access logs
    Review SAP HTTP access logs (transaction SLG1 or web server logs) for CRM_BSP_FRAME requests containing script tags or XSS payloads in parameter values.
    Affected if Logs show requests with malicious script content in parameters targeting the CRM_BSP_FRAME application.

A user is affected if they run a vulnerable SAP NetWeaver version with CRM_BSP_FRAME deployed and accessible, and if the application reflects user input without proper encoding.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply SAP security patches for CVE-2020-6229 and implement proper output encoding for user-controlled inputs in the CRM_BSP_FRAME BSP application.

Fix this in Netweaver As Abap Business Server Pages Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6229 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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