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.
| Vendor | Product | Version(s) | CPE |
|---|---|---|---|
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:-:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p1:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p10:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p11:*:*:*:*:*:* | ||
14.3CPE matchmatch criteria | cpe:2.3:o:freebsd:freebsd:14.3:p12:*:*:*:*:*:* |
CVSS version used by this source: 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
The average CVE in this peer group has 0.0 Twitter, 0.0 Reddit, 0.0 Bluesky, 0.0 Mastodon, and 0.1 GitHub mentions.
No media coverage found for this CVE.
The average CVE in this peer group has 0.1 InfoSec Media, 0.0 Vendor Blog, and 0.0 Security Researcher mentions.
Remediation records are not available for this CVE.