-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Fix CVE-2022-34917 about kafka-client dependency #24097
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
5c7e666 to
7d921b6
Compare
|
I see unit test failures after upgrading Kafka from version 2.3.1 to 2.8.2. (Kafka 2.8.2 fixes CVE-2022-34917)
On log analysis, I see, .github->workflows-> product-tests-basic-environment.yml -> executes presto-product-tests/bin/run_on_docker.sh -> executes presto-product-tests/conf/docker/files/run-tempto.sh run-tempto.sh shell script is used to execute test cases using the TemptoProductTestRunner.java Integration tests for "Presto" is dependent on tempto-kafka/tempto-runner from repo prestodb/tempto. Tempto dependency is using older versions:
Questions: 1. Upgrade Tempto dependencies? 2. Testing Tempto changes (if applicable)
mvn dependency:tree -Dverbose kafka.utils.ZkUtils was removed in
Reference link: |
|
Thanks for the great release note! Just one nit suggestion about kafka as related to #18721. |
|
FYI this PR: #24211 uses the modified tempto with the kafka upgrade changes. All the tests passed. |
|
It looks like there are some test failures: |
3d61ea4 to
0b0c472
Compare
@ZacBlanco I have pushed changes fixing above test cases failure in |
|
@adkharat can you please mark this as ready for review? |
| return resourceConfigFiles; | ||
| } | ||
|
|
||
| @Config("kafka.config.resources") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this new config needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this new config needed?
@pratyakshsharma new config removed
Upgraded version to 3.7.1 upgraded to 3.9.0 fixed presto-kafka test cases excluded io.netty combined exclusion
14977b7 to
8e64e1b
Compare
8e64e1b to
52e6a76
Compare

Description
CVE-2022-34917
Previous Kafka version to 2.3.1
Upgraded Kafka version to 3.9.0
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.
Motivation and Context
Impact
Test Plan
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.