Unauthenticated privileged operations via Shiro RBAC bypass
Published Mar 24, 2025 · Updated Mar 26, 2025
Improper access control in OpenDaylight SFC through Sodium SR4 allows remote attackers to execute privileged operations via crafted requests. Public records identify the Shiro-based RBAC mechanism as the locus but do not disclose which request handler or authorization check fails. No authentication or user interaction is required, and successful requests can affect controller confidentiality, integrity, and availability.
Summary
What happened
Improper access control in OpenDaylight SFC through Sodium SR4 allows remote attackers to execute privileged operations via crafted requests. Public records identify the Shiro-based RBAC mechanism as the locus but do not disclose which request handler or authorization check fails. No authentication or user interaction is required, and successful requests can affect controller confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-29315
- Published
- Mar 24, 2025
- Updated
- Mar 26, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-284, T1068
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2025CVE publishedPublication date reported by the CVE source.
- Mar 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo