# CVE-2018-2499: Information disclosure in SAP Financial Consolidation Cube Designer (BOBJ EADES)

> An attacker can discover the password hash of an admin user in SAP Financial Consolidation Cube Designer, potentially leading to unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-ghf4-f842-9gj7

## What is CVE-2018-2499?

CVE-2018-2499 is a high-severity vulnerability in SAP Financial Consolidation Cube Designer (BOBJ_EADES), published on 8 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security weakness in SAP Financial Consolidation Cube Designer (BOBJ_EADES fixed in versions 8.0, 10.1) may allow an attacker to discover the password hash of an admin user.

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

It affects 2 products.


Products: Sap Financial Consolidation Cube Designer, Sap Financial Consolidation Cube Designer Bobj Eades.

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

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

## Is CVE-2018-2499 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2499 is a high-severity vulnerability in SAP Financial Consolidation Cube Designer (BOBJ_EADES), published on 8 Jan 2019. 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-2018-2499 in the wild and no public exploit code.

Affected product: SAP Financial Consolidation Cube Designer (BOBJ_EADES). 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-2499/ (Markdown: https://insights.sbomify.com/CVE-2018-2499/index.md)
```

## Sources

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

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