p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости golang-1.24 · Страница 5

За последние 30 дней в golang-1.24 опубликовано уязвимостей: 18; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 89

  1. CVE-2025-0913

    Средний · CVSS 5.5EPSS 0,33%Нет опубликованного исправления

    Inconsistent handling of O_CREATE|O_EXCL on Unix and Windows in os in syscall

    os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.

  2. CVE-2025-4673

    Средний · CVSS 6.8EPSS 0,67%Нет опубликованного исправления

    Sensitive headers not cleared on cross-origin redirect in net/http

    Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.

  3. CVE-2025-22874

    Высокий · CVSS 7.5EPSS 0,37%Нет опубликованного исправления

    Usage of ExtKeyUsageAny disables policy validation in crypto/x509

    Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

  4. CVE-2025-22870

    Средний · CVSS 4.4EPSS 0,43%Нет опубликованного исправления

    HTTP Proxy bypass using IPv6 Zone IDs in golang.org/x/net

    Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.

    Опубликовано Обновлено
  5. CVE-2025-22866

    Средний · CVSS 4EPSS 0,29%Нет опубликованного исправления

    Timing sidechannel for P-256 on ppc64le in crypto/internal/nistec

    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 recovery of the private key when P-256 is used in any well known protocols.

    Опубликовано Обновлено
  6. CVE-2025-22865

    Высокий · CVSS 7.5EPSS 0,61%Нет опубликованного исправления

    ParsePKCS1PrivateKey panic with partial keys in crypto/x509

    Using ParsePKCS1PrivateKey to parse a RSA key that is missing the CRT values would panic when verifying that the key is well formed.

    Опубликовано Обновлено
  7. CVE-2024-45336

    Средний · CVSS 6.1EPSS 0,73%Нет опубликованного исправления

    Sensitive headers incorrectly sent after cross-domain redirect in net/http

    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 redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.

    Опубликовано Обновлено
  8. CVE-2024-45340

    Высокий · CVSS 8.8EPSS 0,71%Нет опубликованного исправления

    GOAUTH credential leak in cmd/go

    Credentials provided via the new GOAUTH feature were not being properly segmented by domain, allowing a malicious server to request credentials they should not have access to. By default, unless otherwise set, this only affected credentials stored in the users .netrc file.

    Опубликовано Обновлено
  9. CVE-2024-45341

    Средний · CVSS 6.1EPSS 0,57%Нет опубликованного исправления

    Usage of IPv6 zone IDs can bypass URI name constraints in crypto/x509

    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.

    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →