CVE-2025-29314 json
OpenDaylight SFC Insecure Shiro Cookie Configuration
published last yr. modified 4mo ago also GHSA-xp75-w7vq-5x6j , EUVD-2025-8015
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2025-29314 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.csdn.net https://blog.csdn.net/weixin_43959580/article/details/146018166 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.opendaylight.sfc:odl-sfc-ovs | <=0.10.4 |
no fix listed |
| maven | org.opendaylight.sfc:odl-sfc-openflow-renderer | <=0.10.4 |
no fix listed |
Classification
- Weakness
-
- CWE-311 Missing Encryption of Sensitive Data
References
-
blog.csdn.net
/weixin_43959580/article/details/146018166
exploit, web
-
nvd.nist.gov
/vuln/detail/CVE-2025-29314
advisory
-
github.com
/opendaylight/sfc
package
Sources
- CVE List CVE-2025-29314
- GitHub Advisory GHSA-xp75-w7vq-5x6j
- NVD CVE-2025-29314
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.