OPNsense: Direct comma-separated user privileges bypass OPNsense MVC read-only write protection
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| opnsense | core | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opnsense | Core |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.380% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opnsense
Opnsense core |
|
| Vendors & Products |
Opnsense
Opnsense core |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.11, OPNsense\Core\ACL::hasPrivilege() appends a directly assigned comma-separated <priv> value as one string and then uses an exact comparison when checking user-config-readonly. A user directly assigned both a component write privilege and user-config-readonly can therefore be treated as lacking the read-only restriction, and MVC APIs protected by throwReadOnly() can persist configuration changes for that component. Group privileges are not affected by the same parser flaw because the group path already splits comma-separated values. This issue is fixed in version 26.1.11. | |
| Title | OPNsense: Direct comma-separated user privileges bypass OPNsense MVC read-only write protection | |
| Weaknesses | CWE-863 | |
| References |
|
|
| Metrics |
cvssV3_1
|