CVE-2017-6950
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 GUI 7.2 through 7.5 allows remote attackers to bypass intended security policy restrictions and execute arbitrary code via a crafted ABAP code, aka SAP Security Note 2407616.
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 GUI versions 7.2 through 7.5 contain a vulnerability that allows remote attackers to bypass security policy restrictions by sending crafted ABAP (Advanced Business Application Programming) code, leading to arbitrary code execution on the affected 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= 7.20= 7.30= 7.40_core_sp00-sp011= 7.50_core_sp000CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Identify installed SAP GUI version on WindowsOpen Windows Control Panel > Programs and Features, or right-click the SAP Logon icon and select 'About SAP Logon'. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\SAP\SAPGUI\Version in Windows Registry Editor.Affected if The installed version matches 7.20, 7.30, 7.40 with core SP00 through SP011, or 7.50 with core SP000.
-
Confirm exact version string from SAP LogonLaunch SAP Logon (pad.exe), click the 'SAP Logon' icon in the top-left corner, and select 'About SAP Logon' from the dropdown menu. Note the full version string displayed in the dialog.Affected if The version string reads exactly 7.20, 7.30, 7.40_core_sp00-sp011, or 7.50_core_sp000.
-
Check for installed SAP GUI patchesOpen SAP Logon and navigate to the menu: Help > Support Package > Display. Look for any installed support packages or patches related to security note 2407616.Affected if No security patch corresponding to SAP Note 2407616 is listed as installed, indicating the vulnerability remains unpatched.
-
Verify SAP GUI connectivity configurationOpen SAP Logon and review the configured SAP system entries (servers/landscapes). Check if connections are defined to remote SAP systems.Affected if SAP GUI is configured with active connections to SAP systems, which would allow a remote attacker to send crafted ABAP code through the connection.
-
Inspect SAP GUI security settingsIn SAP Logon, go to Options > Security > Scripting. Check whether ABAP scripting or external program execution features are enabled.Affected if ABAP scripting or related execution features are enabled, allowing crafted ABAP code to be processed by the client.
A system is affected if it runs any unpatched SAP GUI version 7.20, 7.30, 7.40 (core SP00-SP011), or 7.50 (core SP000) with active SAP system connectivity and ABAP execution features 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 SAP Security Note 2407616 patch and upgrade to a non-vulnerable version of SAP GUI. Additionally, restrict network access to SAP systems and enforce least-privilege ABAP execution policies where possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6950 — 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-2017-6950 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