CVE-2020-6262
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 · uneditedService Data Download in SAP Application Server ABAP (ST-PI, before versions 2008_1_46C, 2008_1_620, 2008_1_640, 2008_1_700, 2008_1_710, 740) allows an attacker to inject code that can be executed by the application. An attacker could thereby control the behavior of the application and the whole ABAP system leading to Code Injection.
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 confidenceCode injection vulnerability in SAP Application Server ABAP's Service Data Download component (ST-PI). Attackers can inject malicious code through this service that gets executed by the ABAP application, potentially achieving full control of the ABAP system.
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= 740= 2008_1_46c= 2008_1_620= 2008_1_640= 2008_1_700= 2008_1_710CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SAP Application Server ABAP is runningAccess SAP system information via transaction SM51 or check the SAP kernel version using the 'SAPCAR' utility on the kernel directoryAffected if The system is not SAP Application Server ABAP (the vulnerability only affects ABAP stack)
-
Identify ST-PI component versionUse SAP transaction code SPAM or check the ST-PI version via transaction SAINT (Add-On Installation Tool) by viewing installed support packages for component ST-PI, or query table CPRMX for component version informationAffected if The installed ST-PI version matches 740, 2008_1_46c, 2008_1_620, 2008_1_640, 2008_1_700, or 2008_1_710 exactly
-
Verify Service Data Download is activeCheck transaction SICF for active service path /sap/public/bc/ur/ or use transaction SRT_MANGER to verify ST-PI services are registered in the systemAffected if The Service Data Download component (ST-PI) is enabled and accessible in the ABAP system
The environment is affected if it runs SAP Application Server ABAP with ST-PI component version exactly matching 740, 2008_1_46c, 2008_1_620, 2008_1_640, 2008_1_700, or 2008_1_710 and has the Service Data Download functionality enabled
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 the appropriate SAP ST-PI patch: version 2008_1_46C or higher for the 2008_1_46C track; 2008_1_620 or higher for 2008_1_620; 2008_1_640 or higher for 2008_1_640; 2008_1_700 or higher for 2008_1_700; 2008_1_710 or higher for 2008_1_710; or version 740 or higher.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6262 — 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-6262 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