You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exposure of temporary credentials in logs in Apache Arrow Rust Object Store,
version 0.10.1 and earlier on all platforms using AWS WebIdentityTokens.
On certain error conditions, the logs may contain the OIDC token passed to AssumeRoleWithWebIdentity.
This allows someone with access to the logs to impersonate that identity,
including performing their own calls to AssumeRoleWithWebIdentity, until the
OIDC token expires. Typically OIDC tokens are valid for up to an hour, although
this will vary depending on the issuer.
Users are recommended to use a different AWS authentication mechanism, disable
logging or upgrade to version 0.10.2, which fixes this issue.
Details
When using AWS WebIdentityTokens with the object_store crate, in the event of
a failure and automatic retry, the underlying reqwest error, including the
full URL with the credentials, potentially in the parameters, is written to the
logs.
Thanks to Paul Hatcherian for reporting this vulnerability
object_store
0.7.1
>=0.10.2
<0.5.0
Exposure of temporary credentials in logs in Apache Arrow Rust Object Store,
version 0.10.1 and earlier on all platforms using AWS WebIdentityTokens.
On certain error conditions, the logs may contain the OIDC token passed to
AssumeRoleWithWebIdentity.
This allows someone with access to the logs to impersonate that identity,
including performing their own calls to AssumeRoleWithWebIdentity, until the
OIDC token expires. Typically OIDC tokens are valid for up to an hour, although
this will vary depending on the issuer.
Users are recommended to use a different AWS authentication mechanism, disable
logging or upgrade to version 0.10.2, which fixes this issue.
Details
When using AWS WebIdentityTokens with the
object_store
crate, in the event ofa failure and automatic retry, the underlying
reqwest
error, including thefull URL with the credentials, potentially in the parameters, is written to the
logs.
Thanks to Paul Hatcherian for reporting this vulnerability
See advisory page for additional details.
The text was updated successfully, but these errors were encountered: