{"id":"CVE-2017-18367","published":"2019-04-24T20:02:19Z","modified":"2024-08-05T21:20:50Z","title":"libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them","vendor":null,"product":null,"tier":"tail","description":{"text":"libseccomp-golang 0.9.0 and earlier incorrectly generates BPFs that OR multiple arguments rather than ANDing them. A process running under a restrictive seccomp filter that specified multiple syscall arguments could bypass intended access restrictions by specifying a single matching argument.","provenance":"source","from":"CVE.org"},"cvss":null,"epss":{"score":0.0243,"percentile":0.84635,"provenance":"source"},"cwes":[],"references":[{"url":"https://github.com/seccomp/libseccomp-golang/issues/22","tags":["x_refsource_MISC"]},{"url":"https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e","tags":["x_refsource_MISC"]},{"url":"http://www.openwall.com/lists/oss-security/2019/04/25/6","tags":["mailing-list","x_refsource_MLIST"]},{"url":"https://access.redhat.com/errata/RHSA-2019:4087","tags":["vendor-advisory","x_refsource_REDHAT"]},{"url":"https://access.redhat.com/errata/RHSA-2019:4090","tags":["vendor-advisory","x_refsource_REDHAT"]},{"url":"https://lists.debian.org/debian-lts-announce/2020/08/msg00016.html","tags":["mailing-list","x_refsource_MLIST"]},{"url":"https://usn.ubuntu.com/4574-1/","tags":["vendor-advisory","x_refsource_UBUNTU"]}],"priority":{"score":16.9,"factors":[{"name":"EPSS percentile","points":16.93}]},"affected":[{"ecosystem":"Go","package":"github.com/seccomp/libseccomp-golang","vulnerableRanges":["<0.9.1","<0.9.1-0.20170424173420-06e7a29f36a3"],"patched":["0.9.1","0.9.1-0.20170424173420-06e7a29f36a3"],"from":["GHSA-58v3-j75h-xr49","GO-2020-0007"],"provenance":"source"}],"summary":{"text":"The flaw is in libseccomp-golang, the Go bindings for libseccomp, where version 0.9.0 and earlier incorrectly generate BPF filters that OR multiple syscall arguments together instead of ANDing them. An attacker who controls a process running under such a restrictive seccomp filter can bypass the intended access restrictions by supplying just one argument that matches, with no special network access, authentication, or user interaction described beyond running under the affected filter.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:32:36Z"},"euvd":{"id":"EUVD-2021-0954","exploited":false,"provenance":"source"}}