CVE-2020-6228
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 Business Client, versions 6.5, 7.0, does not perform necessary integrity checks which could be exploited by an attacker under certain conditions to modify the installer.
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 confidenceSAP Business Client versions 6.5 and 7.0 lack proper integrity checks in their installer mechanism, allowing an attacker to potentially modify the installer package under certain conditions. This enables tampering with the software during distribution or download.
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= 6.0= 6.5= 7.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installed SAP Business Client versionOpen SAP Business Client and navigate to Help > About SAP Business Client, or check the installed programs list in Windows Control Panel > Programs and Features to locate the exact version numberAffected if The installed version is 6.0, 6.5, or 7.0 as listed in the affected versions
-
Locate the original installer packageFind the original installer executable (.exe or .msi) that was used to install SAP Business Client, or download a fresh copy from the official SAP Support PortalAffected if The original installer file is available for inspection
-
Verify digital signature on installer fileRight-click the installer executable, select Properties, and inspect the Digital Signatures tab to check if there is a valid signature from SAPAffected if The installer has no digital signature or shows an invalid/broken signature
-
Check for checksum fileLook for a accompanying .md5, .sha1, .sha256, or .asc checksum signature file alongside the downloaded installer in the official download locationAffected if No checksum or signature file accompanies the installer, or the checksum cannot be verified against an official source
-
Inspect installer integrity validationAttempt to modify a minor byte in the installer file and re-run the installer to see if it detects tampering or halts with an integrity error (this should only be done in a test environment with a backup)Affected if The installer runs successfully after the file has been modified, indicating no integrity validation occurs
You are affected if SAP Business Client version 6.0, 6.5, or 7.0 is installed and the installer package lacks verifiable digital signatures or checksum validation to detect tampering.
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 dataUsers should verify installer integrity using official checksums or digital signatures before execution. SAP would need to implement cryptographic integrity verification (e.g., code signing with signature validation) into their installer framework.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6228 — 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-6228 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