Skip to content
Fencer Vulns
high 7.5

CVE-2017-18367 json

Improper Input Validation in libseccomp-golang

published 2019-04-24 7 y ago modified 2026-06-17 4 mo ago also GHSA-58v3-j75h-xr49 , GO-2020-0007 , EUVD-2021-0954

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/seccomp/libseccomp-golang 0.9.1, 0.9.1-0.20170424173420-06e7a29f36a3
  • golang-github-seccomp-libseccomp-golang Debian 14, Debian 13, Debian 12 0.9.0-2

debian advisories DEBIAN-CVE-2017-18367

  • golang-github-seccomp-libseccomp-golang Ubuntu 16.04 LTS 0.0~git20150813.0.1b506fc-2+deb9u1build0.16.04.1

ubuntu advisories UBUNTU-CVE-2017-18367

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • atomic-openshift openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-pod openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-node openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-tests openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-master openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-clients openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-sdn-ovs openshift 3.11 3.11.232-1.git.0.a5bc32f.el7
  • atomic-openshift-excluder openshift 3.11 3.11.232-1.git.0.a5bc32f.el7

red hat advisories RHSA-2020:2479RHSA-2019:4087

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-18367 updated cvss 6.5

libseccomp-golang: mishandling of multiple argument rules leading to a bypass of intended access restrictions

  • Red Hat OpenShift Container Platform 3.10 atomic-openshift, atomic-openshift-pod, atomic-openshift-node, atomic-openshift-tests, atomic-openshift-master, atomic-openshift-clients, +7 more
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 4 openshift-enterprise-node-container
    affected: no fix available
  • Red Hat OpenShift Container Platform 3.11 atomic-openshift 3.11.232-1.git.0.a5bc32f.el7, atomic-openshift-pod 3.11.232-1.git.0.a5bc32f.el7, atomic-openshift-node 3.11.232-1.git.0.a5bc32f.el7, atomic-openshift-tests 3.11.232-1.git.0.a5bc32f.el7, atomic-openshift-master 3.11.232-1.git.0.a5bc32f.el7, atomic-openshift-clients 3.11.232-1.git.0.a5bc32f.el7, +7 more
    fixed: vendor fix RHSA-2020:2479
  • Red Hat OpenShift Container Platform 4.1 openshift4/ose-cli v4.1.27-201912030019, openshift4/ose-hyperkube v4.1.27-201912030019, openshift4/ose-hypershift v4.1.27-201912030019, openshift 4.1.27-201912021146.git.0.a40116f.el7, openshift 4.1.27-201912021146.git.0.a40116f.el8_0, openshift4/ose-cli-artifacts v4.1.27-201912030019, +6 more
    fixed: vendor fix RHSA-2019:4087

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.43% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N
GitHub 3.1 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/seccomp/libseccomp-golang
<0.9.1
<0.9.1-0.20170424173420-06e7a29f36a3
0.9.1
0.9.1-0.20170424173420-06e7a29f36a3

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-284 Improper Access Control

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.