# CVE-2025-42997: Information Disclosure vulnerability in SAP Gateway Client

> A high-privileged user can access restricted information in SAP Gateway Client, potentially impacting confidentiality, integrity, and availability.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2025
- **Updated:** 13 May 2025
- **Also known as:** GHSA-c9j5-3rxr-ch9p

## What is CVE-2025-42997?

CVE-2025-42997 is a medium-severity vulnerability in SAP_SE SAP Gateway Client, published on 13 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Under certain conditions, SAP Gateway Client allows a high-privileged user to access restricted information beyond the scope of the application. Due to the possibility of influencing application behavior or performance through misuse of the exposed data, this may potentially lead to low impact on confidentiality, integrity, and availability.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-42997?


## How do I fix CVE-2025-42997?

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

## Is CVE-2025-42997 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-42997 and fix it if it is affected.

What it is: CVE-2025-42997 is a medium-severity vulnerability in SAP_SE SAP Gateway Client, published on 13 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42997 in the wild and no public exploit code.

Affected product: SAP_SE SAP Gateway Client. 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-2025-42997/ (Markdown: https://insights.sbomify.com/CVE-2025-42997/index.md)
```

## Sources

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

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