Information Exposure Affecting container-tools:4.0/oci-seccomp-bpf-hook package, versions <0:1.2.5-2.module_el8.8.0+3468+16b86c82


Severity

Recommended
0.0
high
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.12% (47th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ALMALINUX8-CONTAINERTOOLS-6243011
  • published12 Feb 2024
  • disclosed30 Apr 2024

Introduced: 12 Feb 2024

CVE-2023-45287  (opens in a new tab)
CWE-203  (opens in a new tab)

How to fix?

Upgrade AlmaLinux:8 container-tools:4.0/oci-seccomp-bpf-hook to version 0:1.2.5-2.module_el8.8.0+3468+16b86c82 or higher.
This issue was patched in ALSA-2024:0748.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:4.0/oci-seccomp-bpf-hook package and not the container-tools:4.0/oci-seccomp-bpf-hook package as distributed by AlmaLinux. See How to fix? for AlmaLinux:8 relevant fixed versions and status.

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits. In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

CVSS Scores

version 3.1