Allocation of Resources Without Limits or Throttling Affecting podman-gvproxy package, versions *
Threat Intelligence
EPSS
0.21% (60th
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 ID SNYK-CENTOS9-PODMANGVPROXY-3041049
- published 7 Oct 2022
- disclosed 4 Oct 2022
Introduced: 4 Oct 2022
CVE-2022-2879 Open this link in a new tabHow to fix?
There is no fixed version for Centos:9 podman-gvproxy.
NVD Description
Note: Versions mentioned in the description apply only to the upstream podman-gvproxy package and not the podman-gvproxy package as distributed by Centos.
See How to fix? for Centos:9 relevant fixed versions and status.
Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.
References
- https://access.redhat.com/security/cve/CVE-2022-2879
- https://access.redhat.com/errata/RHSA-2023:0328
- https://access.redhat.com/errata/RHSA-2023:0446
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/THKJHFMX4DAZXJ5MFPN3BNHZDN7BW5RI/
- https://go.dev/cl/439355
- https://go.dev/issue/54853
- https://groups.google.com/g/golang-announce/c/xtuG5faxtaU
- https://pkg.go.dev/vuln/GO-2022-1037
- https://security.gentoo.org/glsa/202311-09
CVSS Scores
version 3.1