CVE-2025-29314 — odl-sfc-ovs
HIGHCVE-2025-29314 is a high-severity (CVSS 8.1) CWE-311 vulnerability in org.opendaylight.sfc:odl-sfc-ovs. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
OpenDaylight SFC Insecure Shiro Cookie Configuration
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-29314.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.opendaylight.sfc:odl-sfc-ovs☕org.opendaylight.sfc:odl-sfc-openflow-rendererReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Insecure Shiro cookie configurations in OpenDaylight Service Function Chaining (SFC) Subproject SFC Sodium-SR4 and below allow attackers to access sensitive information via a man-in-the-middle attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.opendaylight.sfc:odl-sfc-ovs | all versions | No fix |
| ☕Maven | org.opendaylight.sfc:odl-sfc-openflow-renderer | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opendaylight.sfc:odl-sfc-ovs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.opendaylight.sfc:odl-sfc-ovs for CVE-2025-29314. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-29314 in your dependencies?
Find it across Maven, including transitive dependencies.