Important: git-lfs security update

ELSA-2024-8038: container-tools:ol8 security update (IMPORTANT)

ELSA-2024-3346: git-lfs security update (IMPORTANT)

ELSA-2024-2724: git-lfs security update (IMPORTANT)

ELSA-2024-9115: grafana security update (MODERATE)

Moderate: git-lfs security update

ELSA-2025-7256: git-lfs security update (MODERATE)

If errors returned from MarshalJSON methods contain user controlled data, they may be used to break the contextual auto-escaping behavior of the html/template package, allowing for subsequent actions to inject unexpected content into templates.

Уязвимость пакета html/template языка программирования Go, связанная с отсутствием проверки входных значений, позволяющая нарушителю вводить произвольный контент в шаблоны

Important: container-tools:rhel8 security update

ELSA-2024-5258: container-tools:ol8 security update (IMPORTANT)

A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop.

A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop.

A malformed DNS message in response to a query can cause the Lookup functions to get stuck in an infinite loop.

Malformed DNS message can cause infinite loop in net

A malformed DNS message in response to a query can cause the Lookup fu ...

The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

Denial of service due to improper 100-continue handling in net/http