dbcve.org
Abap PlatformApplication · Sap

CVE-2020-6296

HIGH · 8.8 CVSS v3.1 Published 2020-08-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 (ABAP Server) and ABAP Platform, versions - 700, 701, 702, 710, 711, 730, 731, 740, 750, 751, 753, 755, allows an attacker to inject code that can be executed by the application, leading to Code Injection. An attacker could thereby control the behavior of the application.

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 confidence

A code injection vulnerability in SAP NetWeaver ABAP Server and ABAP Platform allows attackers to inject malicious code that gets executed by the application, enabling complete control over application behavior. The vulnerability affects multiple versions (700-755) and stems from insufficient input validation in ABAP code processing.

MitigationApply SAP security patches for CVE-2020-6296 and conduct code review of ABAP applications to identify and remediate injection-prone input handling patterns.

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
Abap PlatformApplication
Affected:= 7.31= 700= 701= 702= 710= 711= 740= 750= 751= 753= 755
Netweaver Application Server AbapApplication
Affected:= 700= 701= 702= 710= 711= 731= 740= 750= 751= 753= 755

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

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

  1. Identify the ABAP Platform or NetWeaver AS ABAP version
    Execute the SAP transaction SM51 or use the SAP kernel version check (sapkernel -version) to retrieve the exact ABAP platform or NetWeaver AS ABAP release version running on the system
    Affected if The installed version matches any of the following: 7.31, 700, 701, 702, 710, 711, 731, 740, 750, 751, 753, or 755
  2. Review ABAP code that handles external input
    Use transaction SE11, SE80, or SLIN to examine custom ABAP programs that accept user input (parameters, selection screens, dynpro fields, or interface parameters) and pass them to dynamic code execution statements such as INSERT REPORT, GENERATE SUBROUTINE POOL, or CL_ABAP_CODEPAGE=>CONVERT
    Affected if Custom ABAP code processes user-supplied input without proper validation before using dynamic ABAP generation or execution statements
  3. Audit dynamic ABAP generation usage
    Search the ABAP repository (transaction SE14 or using RSABE - or similar repository search tools) for occurrences of statements that allow dynamic code generation including INSERT REPORT, GENERATE REPORT, GENERATE SUBROUTINE POOL, or CL_ABAP_CODEPAGE methods receiving unvalidated input
    Affected if Dynamic ABAP code generation statements exist in the system and accept input from untrusted sources without validation
  4. Inspect transaction SE38 and SABP_ for suspicious program execution
    Review the audit log from transaction SAAB (Security Audit Log) or look at system log (transaction SM37) for executions of ABAP programs that may indicate injected code execution, specifically looking for dynamic program generation or unusual program executions
    Affected if There are logs or traces showing unexpected dynamic program generation or execution of programs not originally deployed by the system administrator

A system is affected if it runs any of the listed ABAP Platform or NetWeaver AS ABAP versions (7.31 through 755) AND contains custom ABAP code that uses dynamic code generation features with unvalidated user input.

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-6296 and conduct code review of ABAP applications to identify and remediate injection-prone input handling patterns.

Fix this in Abap Platform Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6296 — 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-6296 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