Поиск уязвимостей

ALT-PU-2023-1324: package `traefik` update to version 2.9.8-alt1

ALT-PU-2023-1270: package `traefik` update to version 2.9.8-alt1

Traefik is an open source HTTP reverse proxy and load balancer. Versions prior to 2.9.6 are subject to a potential vulnerability in Traefik displaying the Authorization header in its debug logs. In certain cases, if the log level is set to DEBUG, credentials provided using the Authorization header are displayed in the debug logs. Attackers must have access to a users logging system in order for credentials to be stolen. This issue has been addressed in version 2.9.6. Users are advised to upgrade. Users unable to upgrade may set the log level to `INFO`, `WARN`, or `ERROR`.

Traefik is an open source HTTP reverse proxy and load balancer. Versio ...

Traefik may display authorization header in the debug logs

Traefik is an open source HTTP reverse proxy and load balancer. In affected versions there is a potential vulnerability in Traefik managing TLS connections. A router configured with a not well-formatted TLSOption is exposed with an empty TLSOption. For instance, a route secured using an mTLS connection set with a wrong CA file is exposed without verifying the client certificates. Users are advised to upgrade to version 2.9.6. Users unable to upgrade should check their logs to detect the error messages and fix your TLS options.

Traefik is an open source HTTP reverse proxy and load balancer. In aff ...

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.

An attacker can cause excessive memory growth in a Go server accepting ...

Traefik routes exposed with an empty TLSOption

golang.org/x/net/http2 vulnerable to possible excessive memory growth

ELSA-2023-2222: conmon security and bug fix update (MODERATE)

Уязвимость пакета http2 языка программирования Go, позволяющая нарушителю вызвать отказ в обслуживании

Security update for go1.18

Security update for go1.19

ELSA-2023-2367: containernetworking-plugins security and bug fix update (MODERATE)

ELSA-2023-2283: skopeo security and bug fix update (MODERATE)