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
Is your feature request related to a problem? Please describe.
The AWS access token rule matches some strings that cannot be a valid AWS token and should be modified.
Describe the solution you'd like
It was recently discovered that the 16 characters of the token after the 4 character prefix are base32 encoded and include among other things the AWS account number.
The characters used in base32 encoding are letters A-Z and digits 2-7. The regular expression should be modified to only match on these characters, since any that contain 0, 8, or 9 are not valid.
Describe alternatives you've considered
Not applicable, I think.
### Description:
I fixes few issues (gitleaks#1049, gitleaks#1324, gitleaks#1337) and added a rule for AWS Secret
Key.
I renamed the `AWS()` function name to `AWSAccessKey()`, and changed the
`RuleID` too, which may lead to breaking changes ⚠️.
### Checklist:
* [x] Does your PR pass tests?
* [x] Have you written new tests for your changes?
* [x] Have you lint your code locally prior to submission?
Original: gitleaks#1356
Is your feature request related to a problem? Please describe.
The AWS access token rule matches some strings that cannot be a valid AWS token and should be modified.
Describe the solution you'd like
It was recently discovered that the 16 characters of the token after the 4 character prefix are base32 encoded and include among other things the AWS account number.
https://trufflesecurity.com/blog/research-uncovers-aws-account-numbers-hidden-in-access-keys/
The characters used in base32 encoding are letters A-Z and digits 2-7. The regular expression should be modified to only match on these characters, since any that contain 0, 8, or 9 are not valid.
Describe alternatives you've considered
Not applicable, I think.
Additional context
None.
cc @zricethezav
The text was updated successfully, but these errors were encountered: