OPNsense core
OPNsense: Direct comma-separated user privileges bypass OPNsense MVC read-only write protection
Edge device · Firewall / VPNknown edge product: opnsense core OPNsense: Direct comma-separated user privileges (high confidence)
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 26.1.11
Fixed in 26.1.11
Mitigation
Upgrade core to 26.1.11 or later.
References
- Vendor advisory github.com/opnsense/core/security/advisories/G…
- Patch github.com/opnsense/core/commit/578e025111161f…
- Patch github.com/opnsense/core/commit/e15a8849737463…
1 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.