# CVE-2025-42955: Missing authorization check in SAP Cloud Connector

> An attacker on an adjacent network can cause reduced service performance by exploiting a missing authorization check in the LDAP testing endpoint.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2025
- **Updated:** 13 Aug 2025
- **Also known as:** GHSA-6vrh-fhx3-hm46

## What is CVE-2025-42955?

CVE-2025-42955 is a low-severity missing authorization vulnerability in SAP_SE SAP Cloud Connector, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Due to a missing authorization check in SAP Cloud Connector, an attacker on an adjacent network with low privileges could send a crafted request to the endpoint responsible for testing LDAP connections. A successful exploit could lead to reduced performance, hence a low-impact on availability of the service. Confidentiality and integrity of the data are not affected.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-42955 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-42955 is a low-severity missing authorization vulnerability in SAP_SE SAP Cloud Connector, published on 12 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-42955 in the wild and no public exploit code.

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

## Sources

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

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