# CVE-2025-29315: OpenDaylight SFC Allows Unauthorized Privileged Execution via Crafted Request

> Attackers can execute privileged operations in OpenDaylight SFC due to flawed RBAC checks, requiring an upgrade to secure the system.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-x65v-g96x-c6gw

## What is CVE-2025-29315?

CVE-2025-29315 is a critical missing authorization vulnerability in n/a, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the Shiro-based RBAC (Role-based Access Control) mechanism of OpenDaylight Service Function Chaining (SFC) Subproject SFC Sodium-SR4 and below allows attackers to execute privileged operations via a crafted request.

Weakness: CWE-284 (Improper Access Control)

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

2 open source packages ship an affected version, including org.opendaylight.sfc:sfc-parent.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.opendaylight.sfc:sfc-parent` | Maven | All versions to 0.10.4 | None |
| `org.opendaylight.sfc:sfc-parent` | Maven | All versions to 0.10.4 | None |

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

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

## Is CVE-2025-29315 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29315 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-29315 is a critical missing authorization vulnerability in n/a, published on 24 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29315 exists.

Affected packages and fixed versions:
- org.opendaylight.sfc:sfc-parent (Maven): affected all versions up to 0.10.4; no fix listed
- org.opendaylight.sfc:sfc-parent (Maven): affected all versions up to 0.10.4; no fix listed

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-29315/ (Markdown: https://insights.sbomify.com/CVE-2025-29315/index.md)
```

## Sources

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

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