CVE-2020-6362

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of service disruption.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-10-20 14:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 03:23 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 6.5 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-10-20 14:15 UTC

Last modified

2026-06-17 03:23 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-863 · Incorrect authorization

Record status

Modified

Affected

• Sap Banking Services 500

Attack profile CVSS 3.1 · 6.5

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-6362.md and follow it. Check whether this project is affected by CVE-2020-6362. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge