Information Exposure Affecting criu-libs package, versions <0:3.18-4.module+el8.9.0+90147+a4870853
Threat Intelligence
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 ID SNYK-ORACLE8-CRIULIBS-6249210
- published 16 Feb 2024
- disclosed 5 Dec 2023
Introduced: 5 Dec 2023
CVE-2023-45287 Open this link in a new tabHow to fix?
Upgrade Oracle:8 criu-libs to version 0:3.18-4.module+el8.9.0+90147+a4870853 or higher.
This issue was patched in ELSA-2024-2988.
NVD Description
Note: Versions mentioned in the description apply only to the upstream criu-libs package and not the criu-libs package as distributed by Oracle.
See How to fix? for Oracle: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.
References
- https://linux.oracle.com/cve/CVE-2023-45287.html
- https://linux.oracle.com/errata/ELSA-2024-0748.html
- https://linux.oracle.com/errata/ELSA-2024-2988.html
- https://go.dev/cl/326012/26
- https://go.dev/issue/20654
- https://groups.google.com/g/golang-announce/c/QMK8IQALDvA
- https://people.redhat.com/~hkario/marvin/
- https://pkg.go.dev/vuln/GO-2023-2375
- https://security.netapp.com/advisory/ntap-20240112-0005/