Описание
ELSA-2024-12262: olcne security update (IMPORTANT)
[1.8.1-2]
- Cleanup spec file
[1.8.1-1]
- Fix OLM upgrade failure - upgrade from 0.17.0 to 0.23.1 failed due to a couple of crds missing
- Add hostpathRequiresPrivilged value to rook template cr to be passed to module operator
- Fixed Istio-1.18 and Istio-1.19 installation on aarch64 architecture
- Fixed unable to deploy new module(s) using config file containing already existing modules
- Corrected olcne repo version in the prompt text of the 'olcnectl provision' command
- Update modules and components built with golang 1.20.12 to address CVE-2023-39326
- add conmon resource to kubernetes module
- Fix OLM upgrade failure - same version upgrade failure
- Migrate ModuleOperator from verrazzano-install to ocne-modules namespace
- Fix multiple install during provision
Обновленные пакеты
Oracle Linux 9
Oracle Linux aarch64
olcne-agent
1.8.1-2.el9
olcne-api-server
1.8.1-2.el9
olcne-calico-chart
1.8.1-2.el9
olcne-gluster-chart
1.8.1-2.el9
olcne-grafana-chart
1.8.1-2.el9
olcne-istio-chart
1.8.1-2.el9
olcne-kubevirt-chart
1.8.1-2.el9
olcne-metallb-chart
1.8.1-2.el9
olcne-multus-chart
1.8.1-2.el9
olcne-nginx
1.8.1-2.el9
olcne-oci-ccm-chart
1.8.1-2.el9
olcne-olm-chart
1.8.1-2.el9
olcne-prometheus-chart
1.8.1-2.el9
olcne-rook-chart
1.8.1-2.el9
olcne-utils
1.8.1-2.el9
olcnectl
1.8.1-2.el9
Oracle Linux x86_64
olcne-agent
1.8.1-2.el9
olcne-api-server
1.8.1-2.el9
olcne-calico-chart
1.8.1-2.el9
olcne-gluster-chart
1.8.1-2.el9
olcne-grafana-chart
1.8.1-2.el9
olcne-istio-chart
1.8.1-2.el9
olcne-kubevirt-chart
1.8.1-2.el9
olcne-metallb-chart
1.8.1-2.el9
olcne-multus-chart
1.8.1-2.el9
olcne-nginx
1.8.1-2.el9
olcne-oci-ccm-chart
1.8.1-2.el9
olcne-olm-chart
1.8.1-2.el9
olcne-prometheus-chart
1.8.1-2.el9
olcne-rook-chart
1.8.1-2.el9
olcne-utils
1.8.1-2.el9
olcnectl
1.8.1-2.el9
Связанные CVE
Связанные уязвимости
A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small.
A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small.
A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small.
A malicious HTTP sender can use chunk extensions to cause a receiver r ...
A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real body to encoded bytes grows too small.