[ 
https://issues.apache.org/jira/browse/HADOOP-19764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Loughran updated HADOOP-19764:
------------------------------------
    Description: 

https://github.com/advisories/GHSA-x44p-gvrj-pj2r

Note: this CVE only becomes possible 
* S3A Connector is being used with S3-CSE client side encryption
* When the encrypted data key (EDK) is stored in an "Instruction File" instead 
of S3's metadata record
* the attacker has write access to the bucket.

This is pretty niche. If the attacker has write access to the bucket, they can 
do a lot of damage

  was:
https://github.com/apache/hadoop/blob/trunk/hadoop-project/pom.xml#L214

https://github.com/advisories/GHSA-x44p-gvrj-pj2r

Note: this CVE only becomes possible When the encrypted data key (EDK) is 
stored in an "Instruction File" instead of S3's metadata record *and* the 
attacker has write access to the bucket.


> upgrade amazon-s3-encryption-client-java to 4.0.0+ due to Invisible 
> Salamanders (CVE-2025-14763)
> ------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-19764
>                 URL: https://issues.apache.org/jira/browse/HADOOP-19764
>             Project: Hadoop Common
>          Issue Type: Task
>            Reporter: PJ Fanning
>            Priority: Major
>              Labels: pull-request-available
>
> https://github.com/advisories/GHSA-x44p-gvrj-pj2r
> Note: this CVE only becomes possible 
> * S3A Connector is being used with S3-CSE client side encryption
> * When the encrypted data key (EDK) is stored in an "Instruction File" 
> instead of S3's metadata record
> * the attacker has write access to the bucket.
> This is pretty niche. If the attacker has write access to the bucket, they 
> can do a lot of damage



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to