-
Notifications
You must be signed in to change notification settings - Fork 1.7k
JS: Improved modeling of aws-sdk
#19364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you tried with a sinkModel
like this?
- `["aws-sdk", "", "AnyMember.Argument[0].Member[secretAccessKey]", "credentials-key"]
- `["aws-sdk", "", "Member[Credentials].Argument[1]", "credentials-key"]
As discussed offline, secret scanning should cover this in practice so we shouldn't spend much time on it. I was going to suggest merging it anyway if it was a simple change as there can be other use-cases for recognising non-constant credential sinks. I'm just not sure why it was done like this. Perhaps we should just quickly move on from this one.
…global credentials and AWS.Credentials
This pull request adds support for detecting specific patterns in the use of
aws-sdk
related to hardcoded credentials. The following cases are now identified:AWS.config
object with hardcoded credentials.AWS.ServiceName
instances while passing hardcoded credentials.AWS.Credentials
object.