sigqueue(2) missing capability mode restriction
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in p15, p6 and p10.
sigqueue(2) was marked as permitted in capability mode with the introduction of Capsicum in 2011, but the implementation of kern_sigqueue did not include a capability mode check restricting signal delivery to the calling process's own PID. A process in capability mode can use sigqueue(2) to send signals to any process it could signal following standard Unix permissions, bypassing the Capsicum sandbox restriction. A compromised sandboxed process could interfere with other processes, for example by sending SIGKILL or SIGSTOP. This could be any process running as the same user, or any process, for a superuser sandboxed process.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| FreeBSD | >=14.3-RELEASE <p15, >=14.4-RELEASE <p6, >=15.0-RELEASE <p10 | p15, p6, p10 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket