rdblue opened a new issue, #16470: URL: https://github.com/apache/iceberg/issues/16470
> 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 REST `/v1/config` merge lets a server steer transport, headers, proxying, and auth behavior for the entire client session. # Affected Maven coordinates * primary shipped client artifact: `org.apache.iceberg:iceberg-core` # 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 initial config response can redirect all subsequent catalog traffic to another URI, override or suppress Authorization, force proxy settings, or steer OAuth token refresh/fetch behavior. * This yields credential exfiltration or session hijack even if no gadget class is available. # Proof status Source review only. The issue is visible directly from source. # Key source references * org.apache.iceberg.rest.responses.ConfigResponse * org.apache.iceberg.rest.RESTSessionCatalog * org.apache.iceberg.rest.RESTUtil * org.apache.iceberg.rest.HTTPClient * org.apache.iceberg.rest.auth.BasicAuthManager * org.apache.iceberg.rest.auth.OAuth2Manager 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]
