You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Manikumar <ma...@apache.org> on 2022/09/19 15:53:08 UTC
CVE-2022-34917: Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers
Severity: High
Description:
A security vulnerability has been identified in Apache Kafka. It
affects all releases since 2.8.0. The vulnerability allows malicious
unauthenticated clients to allocate large amounts of memory on
brokers. This can lead to brokers hitting OutOfMemoryException and
causing denial of service.
Example scenarios:
- Kafka cluster without authentication: Any clients able to establish
a network connection to a broker can trigger the issue.
- Kafka cluster with SASL authentication: Any clients able to
establish a network connection to a broker, without the need for valid
SASL credentials, can trigger the issue.
- Kafka cluster with TLS authentication: Only clients able to
successfully authenticate via TLS can trigger the issue.
We advise the users to upgrade the Kafka installations to one of the
3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.
Credit:
Apache Kafka would like to thank Mickael Maison, Tom Bentley and
Daniel Collins for reporting this issue.
References:
https://kafka.apache.org/cve-list
Re: CVE-2022-34917: Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers
Posted by Luke Chen <sh...@gmail.com>.
What a great finding!
Thanks Mickael Maison, Tom Bentley and Daniel Collins!
And thanks for all the release managers who help drive all these security
patch releases!
Luke
On Mon, Sep 19, 2022 at 11:53 PM Manikumar <ma...@apache.org> wrote:
> Severity: High
>
> Description:
>
> A security vulnerability has been identified in Apache Kafka. It
> affects all releases since 2.8.0. The vulnerability allows malicious
> unauthenticated clients to allocate large amounts of memory on
> brokers. This can lead to brokers hitting OutOfMemoryException and
> causing denial of service.
>
> Example scenarios:
> - Kafka cluster without authentication: Any clients able to establish
> a network connection to a broker can trigger the issue.
> - Kafka cluster with SASL authentication: Any clients able to
> establish a network connection to a broker, without the need for valid
> SASL credentials, can trigger the issue.
> - Kafka cluster with TLS authentication: Only clients able to
> successfully authenticate via TLS can trigger the issue.
>
> We advise the users to upgrade the Kafka installations to one of the
> 3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.
>
> Credit:
>
> Apache Kafka would like to thank Mickael Maison, Tom Bentley and
> Daniel Collins for reporting this issue.
>
> References:
>
> https://kafka.apache.org/cve-list
>
Re: CVE-2022-34917: Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers
Posted by Luke Chen <sh...@gmail.com>.
What a great finding!
Thanks Mickael Maison, Tom Bentley and Daniel Collins!
And thanks for all the release managers who help drive all these security
patch releases!
Luke
On Mon, Sep 19, 2022 at 11:53 PM Manikumar <ma...@apache.org> wrote:
> Severity: High
>
> Description:
>
> A security vulnerability has been identified in Apache Kafka. It
> affects all releases since 2.8.0. The vulnerability allows malicious
> unauthenticated clients to allocate large amounts of memory on
> brokers. This can lead to brokers hitting OutOfMemoryException and
> causing denial of service.
>
> Example scenarios:
> - Kafka cluster without authentication: Any clients able to establish
> a network connection to a broker can trigger the issue.
> - Kafka cluster with SASL authentication: Any clients able to
> establish a network connection to a broker, without the need for valid
> SASL credentials, can trigger the issue.
> - Kafka cluster with TLS authentication: Only clients able to
> successfully authenticate via TLS can trigger the issue.
>
> We advise the users to upgrade the Kafka installations to one of the
> 3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.
>
> Credit:
>
> Apache Kafka would like to thank Mickael Maison, Tom Bentley and
> Daniel Collins for reporting this issue.
>
> References:
>
> https://kafka.apache.org/cve-list
>