SAP Business Objects Business Intelligence Platform (CMS / Auditing issues), version 4.2, allows attacker to send specially crafted GIOP pa…

published 2020-04-14 6y ago modified 2026-06-17 4mo ago also EUVD-2020-27377

cvss: 5.3; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 58%
public exploits: 0; none known

SAP Business Objects Business Intelligence Platform (CMS / Auditing issues), version 4.2, allows attacker to send specially crafted GIOP packets to several services due to Improper Input Validation, allowing to forge additional entries in GLF log files.

Is CVE-2020-6227 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	5.3	CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

SAP SE SAP Business Objects Business Intelligence Platform (CMS / Auditing issues)

Classification

Weakness

CWE-20 Improper Input Validation
CWE-116 Improper Encoding or Escaping of Output

References

wiki.scn.sap.com /wiki/pages/viewpage.action?pageId=544214202
vendor-advisory
launchpad.support.sap.com /#/notes/2863396
permissions-required, vendor-advisory

Sources

CVE List CVE-2020-6227
NVD CVE-2020-6227

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.