# CVE-2018-2448: Information disclosure in SAP SRM-MDM CATALOG

> An attacker can access restricted user existence information in SAP SRM-MDM Catalog utilities, potentially aiding further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 14 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4wfj-6vjj-87rj

## What is CVE-2018-2448?

CVE-2018-2448 is a medium-severity vulnerability in SAP SRM-MDM CATALOG, published on 14 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Under certain conditions SAP SRM-MDM (CATALOG versions 3.0, 7.01, 7.02) utilities functionality allows an attacker to access information of user existence which would otherwise be restricted.

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

It affects 1 product.


Products: Sap Supplier Relationship Management Mdm Catalog.

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

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

## Is CVE-2018-2448 being exploited?

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

## Other vulnerabilities in SAP SRM-MDM CATALOG

- [CVE-2018-2449](https://insights.sbomify.com/CVE-2018-2449/): Auth bypass in SAP Supplier Relationship Management Master Data Management Catalog (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2448 is a medium-severity vulnerability in SAP SRM-MDM CATALOG, published on 14 Aug 2018. 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-2448 in the wild and no public exploit code.

Affected product: SAP SRM-MDM CATALOG. 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-2448/ (Markdown: https://insights.sbomify.com/CVE-2018-2448/index.md)
```

## Sources

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

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