# CVE-2025-0067: Missing Authorization check in SAP NetWeaver Application Server Java

> An attacker with standard user privileges can create JCo connection entries due to missing authorization checks, impacting confidentiality, integrity, and availability.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 14 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-wv5f-24hf-9846

## What is CVE-2025-0067?

CVE-2025-0067 is a medium-severity missing authorization vulnerability in SAP_SE SAP NetWeaver Application Server Java, published on 14 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to a missing authorization check on service endpoints in the SAP NetWeaver Application Server Java, an attacker with standard user role can create JCo connection entries, which are used for remote function calls from or to the application server. This could lead to low impact on confidentiality, integrity, and availability of the application.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2025-0067 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0067 is a medium-severity missing authorization vulnerability in SAP_SE SAP NetWeaver Application Server Java, published on 14 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0067 in the wild and no public exploit code.

Affected product: SAP_SE SAP NetWeaver Application Server Java. 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-0067/ (Markdown: https://insights.sbomify.com/CVE-2025-0067/index.md)
```

## Sources

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

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