-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HADOOP-19764. Upgrade amazon-s3-encryption-client-java to 4.0.0+ due to Invisible Salamanders (CVE-2025-14763) #8158
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: trunk
Are you sure you want to change the base?
Conversation
…to Invisible Salamanders (CVE-2025-14763)
|
💔 -1 overall
This message was automatically generated. |
|
AWS SDK team breaking existing code again. |
|
This updates the aws sdk. Is that needed? if so, -1 to the patch as is. Upgrading an aws sdk is a nightmare which usually takes 4+ weeks, automated and manual regression testing with multiple s3 endpoints (s3, s3 express, third party) and as many options in the test matrix as possible (vpce, fips, encryption), then deciding how to react to the regressions which surface. Which do surface, almost always. SDK upgrades cost me about 8 weeks last year. No rush to repeat |
|
I misread https://mvnrepository.com/artifact/software.amazon.encryption.s3/amazon-s3-encryption-client-java/4.0.0 - it looks like we don't need to upgrade the AWS SDK jars, so I'll revert that part of the change. |
d2aa107 to
f3a3744
Compare
|
💔 -1 overall
This message was automatically generated. |
|
you reverted the use of the builder changes? |
I've added the builder change back. I mistakenly thought the code removal issue was with the AWS SDK but the issue is in amazon-s3-encryption-client-java. |
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
Description of PR
CVE-2025-14763
How was this patch tested?
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?