rdblue opened a new issue, #16460: URL: https://github.com/apache/iceberg/issues/16460
> 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 AWS remote signer client keeps auth and HTTP state in static process-wide fields, so one catalog can leak headers or auth behavior into another. # Affected Maven coordinates * primary shipped client artifact: `org.apache.iceberg:iceberg-aws` * bundle artifact: `org.apache.iceberg:iceberg-aws-bundle` # Attacker prerequisites * a shared process that talks to more than one catalog or reuses cached table state * ability to trigger the affected initialization or cache-reuse path # Impact * Cross-tenant leakage of custom auth headers or tokens to the wrong signer service * Authentication confusion when multiple catalogs use different auth mechanisms * Hard-to-detect authorization failures or unintended access if two catalogs share one JVM # Proof status Source review only. The issue is visible directly from source. # Key source references * org.apache.iceberg.aws.s3.signer.S3V4RestSignerClient Current severity assessment [2]: Important [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]
