core: OPNsense: Direct comma-separated user privileges bypass OPNsense MVC read-only write protection
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
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.
Text from CVE List
Affected versions 1
- coreaffected: < 26.1.11CVE List
References 4
- github.com/opnsense/core/commit/578e025111161ffd03fd3fd0ccdac203be546505Fixvia CVE List
- github.com/opnsense/core/commit/e15a884973746319e79bd2cd421e8a015cc3ddb9Fixvia CVE List
- github.com/opnsense/core/commit/f674f4ff294a3f7c4cd0591563f6df47bea50034Fixvia CVE List
- github.com/opnsense/core/security/advisories/GHSA-p9pr-782r-w2xwExploitvia CVE List