cve.bz

CVE-2020-6228 sap business client

7.5 highEPSS 0.4%

High (7.5) in sap business client. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
SAP 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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-354 Improper Validation of Integrity Check Value
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-6228 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-6228?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-6228?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-6228 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
sap:business_client6.0
sap:business_client6.0:patch_level1
sap:business_client6.0:patch_level10
sap:business_client6.0:patch_level11
sap:business_client6.0:patch_level12
sap:business_client6.0:patch_level13
sap:business_client6.0:patch_level14
sap:business_client6.0:patch_level15
sap:business_client6.0:patch_level16
sap:business_client6.0:patch_level17
sap:business_client6.0:patch_level2
sap:business_client6.0:patch_level3
sap:business_client6.0:patch_level4
sap:business_client6.0:patch_level5
sap:business_client6.0:patch_level6
sap:business_client6.0:patch_level7
sap:business_client6.0:patch_level8
sap:business_client6.0:patch_level9
sap:business_client6.5
sap:business_client6.5:patch_level1
sap:business_client6.5:patch_level10
sap:business_client6.5:patch_level11
sap:business_client6.5:patch_level12
sap:business_client6.5:patch_level13
sap:business_client6.5:patch_level14
sap:business_client6.5:patch_level15
sap:business_client6.5:patch_level16
sap:business_client6.5:patch_level17
sap:business_client6.5:patch_level18
sap:business_client6.5:patch_level19
sap:business_client6.5:patch_level2
sap:business_client6.5:patch_level3
sap:business_client6.5:patch_level4
sap:business_client6.5:patch_level5
sap:business_client6.5:patch_level6
sap:business_client6.5:patch_level7
sap:business_client6.5:patch_level8
sap:business_client6.5:patch_level9
sap:business_client7.0
sap:business_client7.0:patch_level1
sap:business_client7.0:patch_level2
sap:business_client7.0:patch_level3
sap:business_client7.0:patch_level4
sap:business_client7.0:patch_level5
sap:business_client7.0:patch_level6

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON