VYPR

apk package

chainguard/go-fips-1.23

pkg:apk/chainguard/go-fips-1.23

Vulnerabilities (6)

  • CVE-2025-61725HigOct 29, 2025
    affected < 1.23.12-r1fixed 1.23.12-r1

    The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

  • CVE-2025-58183MedOct 29, 2025
    affected < 1.23.12-r1fixed 1.23.12-r1

    tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When r

  • CVE-2025-61724Oct 29, 2025
    affected < 1.23.12-r1fixed 1.23.12-r1

    The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption.

  • CVE-2025-22866MedFeb 6, 2025
    affected < 1.23.6-r0fixed 1.23.6-r0

    Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recover

  • CVE-2024-45341MedJan 28, 2025
    affected < 1.23.5-r0fixed 1.23.5-r0

    A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain. Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs.

  • CVE-2024-45336MedJan 28, 2025
    affected < 1.23.5-r0fixed 1.23.5-r0

    The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain re