# CVE-2020-6301: Missing authorization in SAP ERP (HCM Travel Management)

> An authenticated but unauthorized attacker can read, modify, and settle trips in SAP ERP HCM, leading to privilege escalation.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jrpm-x59j-5pxj

## What is CVE-2020-6301?

CVE-2020-6301 is a medium-severity missing authorization vulnerability in SAP ERP (HCM Travel Management), published on 12 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP ERP (HCM Travel Management), versions - 600, 602, 603, 604, 605, 606, 607, 608, allows an authenticated but unauthorized attacker to read, modify and settle trips, resulting in escalation of privileges, due to Missing Authorization Check.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Sap Hcm Travel Management.

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

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

## Is CVE-2020-6301 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6301 is a medium-severity missing authorization vulnerability in SAP ERP (HCM Travel Management), published on 12 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6301 in the wild and no public exploit code.

Affected product: SAP ERP (HCM Travel Management). 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-6301/ (Markdown: https://insights.sbomify.com/CVE-2020-6301/index.md)
```

## Sources

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

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