Back

HIGH

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

Published Apr 24, 2019

Description

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.

Affected products

Remediation

Red Hat statement

This issue may affect OpenShift Container Platform 3.x and 4.x if you are providing a custom Seccomp profile using Security Context Constraints [1]. The custom Seccomp profile would need to specify multiple arguments, such as below, from [2]. { "names": [ "socketcall" ], "action": "SCMP_ACT_ALLOW", "args": [ { "index": 0, "value": 1, "valueTwo": 0, "op": "SCMP_CMP_EQ" }, { "index": 1, "value": 1, "valueTwo": 0, "op": "SCMP_CMP_EQ" } ], "comment": "", "includes": {}, "excludes": {} }, If such a profile was used the arguments could be combined as an OR rule, not AND, as the user might expect from Seccomp. [1] https://docs.openshift.com/container-platform/4.1/authentication/managing-security-context-constraints.html [2] https://github.com/moby/moby/issues/32714#issuecomment-295532163

Metrics

References (12)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner mitre
Published Apr 24, 2019
Updated Aug 5, 2024
Reserved Apr 24, 2019
NVD
Status Modified
Modified Jun 17, 2026
Red Hat
Severity Moderate
Public date Apr 24, 2019
GHSA-58V3-J75H-XR49