USN-9069-1: libseccomp-golang vulnerability
It was discovered that libseccomp-golang incorrectly generated BPF filters for rules that specified multiple syscall arguments, matching any one of the arguments instead of all of them. An attacker could possibly use this issue to bypass intended seccomp restrictions.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/golang-github-seccomp-libseccomp-golang-devto a version that resolves this vulnerability.Fixed in Ubuntu Pro - Upgrade
Upgrade
ubuntu/golang-github-seccomp-libseccomp-golangto a version that resolves this vulnerability.Fixed in 0.9.0-1ubuntu0.1~esm1
Event History
Frequently Asked Questions
What conditions are required for this issue to be exploitable?
The affected application must use libseccomp-golang to generate a seccomp rule with multiple syscall-argument conditions. The risk arises when the policy relies on all of those argument conditions being enforced together.
What is the practical impact on a seccomp policy?
A rule intended to match only when all specified syscall arguments match may instead match when any one argument matches. This can allow an attacker to bypass intended seccomp restrictions.
How can I assess whether my application is exposed?
Review seccomp policies generated through libseccomp-golang for rules that specify multiple syscall arguments. Policies containing only single-argument rules are not described as affected by this issue.