# CVE-2020-6271: Missing authorization in SAP Solution Manager (Problem Context Manager)

> Unauthenticated attackers can cause denial of service and read restricted diagnostic files in SAP Solution Manager.

- **Severity:** High 8.2 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5qf2-fv97-vff9

## What is CVE-2020-6271?

CVE-2020-6271 is a high-severity missing authorization vulnerability in SAP Solution Manager (Problem Context Manager), published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP Solution Manager (Problem Context Manager), version 7.2, does not perform the necessary authentication, allowing an attacker to consume large amounts of memory, causing the system to crash and read restricted data (files visible for technical administration users of the diagnostics agent).

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2020-6271?

It affects 1 product.


Products: Sap Solution Manager.

## How do I fix CVE-2020-6271?

No fix has been published for CVE-2020-6271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-6271 being exploited?

There is no known exploitation of CVE-2020-6271 in the wild and no public exploit code.

## Other vulnerabilities in SAP Solution Manager (Problem Context Manager)

- [CVE-2020-6207](https://insights.sbomify.com/CVE-2020-6207/): SAP Solution Manager Missing Authentication for Critical Function (critical 10.0, exploited in the wild)
- [CVE-2020-26821](https://insights.sbomify.com/CVE-2020-26821/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26822](https://insights.sbomify.com/CVE-2020-26822/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26823](https://insights.sbomify.com/CVE-2020-26823/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)
- [CVE-2020-26824](https://insights.sbomify.com/CVE-2020-26824/): Missing authorization in SAP Solution Manager (JAVA stack) (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6271 and fix it if it is affected.

What it is: CVE-2020-6271 is a high-severity missing authorization vulnerability in SAP Solution Manager (Problem Context Manager), published on 10 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6271 in the wild and no public exploit code.

Affected product: SAP Solution Manager (Problem Context Manager). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-6271/ (Markdown: https://insights.sbomify.com/CVE-2020-6271/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-6271
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-6271
- OSV: https://osv.dev/vulnerability/CVE-2020-6271

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-6271/
Summaries are generated and may contain mistakes; the official description above is the record.