Improper Input Validation Affecting gvisor-tap-vsock package, versions <6:0.7.3-3.el9_4
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-CENTOS9-GVISORTAPVSOCK-6749159
- published 1 May 2024
- disclosed 5 Mar 2024
Introduced: 5 Mar 2024
CVE-2023-45290 Open this link in a new tabHow to fix?
Upgrade Centos:9
gvisor-tap-vsock
to version 6:0.7.3-3.el9_4 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream gvisor-tap-vsock
package and not the gvisor-tap-vsock
package as distributed by Centos
.
See How to fix?
for Centos:9
relevant fixed versions and status.
When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not applied to the memory consumed while reading a single form line. This permits a maliciously crafted input containing very long lines to cause allocation of arbitrarily large amounts of memory, potentially leading to memory exhaustion. With fix, the ParseMultipartForm function now correctly limits the maximum size of form lines.
References
- https://access.redhat.com/security/cve/CVE-2023-45290
- https://go.dev/cl/569341
- https://go.dev/issue/65383
- https://groups.google.com/g/golang-announce/c/5pwGVUPoMbg
- https://pkg.go.dev/vuln/GO-2024-2599
- https://security.netapp.com/advisory/ntap-20240329-0004/
- http://www.openwall.com/lists/oss-security/2024/03/08/4