# CVE-2018-2455: Missing authorization in SAP Enterprise Financial Services

> An authenticated user can escalate privileges due to missing authorization checks in SAP Enterprise Financial Services.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8576-fpqm-f7vg

## What is CVE-2018-2455?

CVE-2018-2455 is a high-severity missing authorization vulnerability in SAP Enterprise Financial Services, published on 11 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SAP Enterprise Financial Services, versions 6.05, 6.06, 6.16, 6.17, 6.18, 8.0 (in business function EAFS_BCA_BUSOPR_SEPA) does not perform necessary authorization checks for an authenticated user, resulting in escalation of privileges.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2018-2455?

It affects 1 product.


Products: Sap Enterprise Financial Services.

## How do I fix CVE-2018-2455?

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

## Is CVE-2018-2455 being exploited?

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

## Other vulnerabilities in SAP Enterprise Financial Services

- [CVE-2018-2454](https://insights.sbomify.com/CVE-2018-2454/): Missing authorization in SAP Enterprise Financial Services (high 8.8)
- [CVE-2021-21486](https://insights.sbomify.com/CVE-2021-21486/): Missing authorization in SAP Enterprise Financial Services (Bank Customer Accounts) (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2455 and fix it if it is affected.

What it is: CVE-2018-2455 is a high-severity missing authorization vulnerability in SAP Enterprise Financial Services, published on 11 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2455 in the wild and no public exploit code.

Affected product: SAP Enterprise Financial Services. 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-2018-2455/ (Markdown: https://insights.sbomify.com/CVE-2018-2455/index.md)
```

## Sources

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

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