rdblue opened a new issue, #16465:
URL: https://github.com/apache/iceberg/issues/16465

   > This issue was reported to the private Apache Iceberg security mailing 
list. The submitter is being kept anonymous because the report was sent to a 
private list. After review, the issue is not considered a serious vulnerability 
that needs to be kept private, so it is being filed publicly here for tracking 
and resolution.
   >
   > Note: this submission was generated by AI. Please review its claims and 
source references carefully before acting on them.
   
   # Summary
   
   The Key Vault client accepts any configured vault URL and
   authenticates with ambient Azure credentials, turning mis-scoped
   config into token exfiltration risk.
   
   # Affected Maven coordinates
   
   * primary shipped client artifact: `org.apache.iceberg:iceberg-azure`
   * bundle artifact: `org.apache.iceberg:iceberg-azure-bundle`
   
   # Attacker prerequisites
   
   * control over the affected catalog response, configuration surface,
   or spec-consumed routing value
   * a client or service that honors the affected configuration without
   an additional allow-list
   
   # Impact
   
   * A malicious or mis-scoped configuration can redirect Key Vault
   authentication traffic to a non-Key-Vault endpoint.
   * That can expose bearer tokens or other auth context to an
   attacker-controlled service.
   * This is less exposed than the ADLS location issue because it is
   config-driven rather than metadata-driven, but it is still an
   endpoint-trust break.
   
   # Proof status
   
   I reproduced this locally with a targeted reproducer or exploit.
   The observed result matches the trigger and impact described above.
   
   # Key source references
   
   * org.apache.iceberg.azure.AzureProperties
   * org.apache.iceberg.azure.keymanagement.AzureKeyManagementClient
   
   Current severity assessment [2]: Moderate
   
   [1] https://iceberg.apache.org/security/
   [2] https://security.apache.org/blog/severityrating/


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to