Open pepdekpd opened 7 months ago
Hi @pepdekpd ,
Thank you for your inputs! Our internal AppSec team will check it soon. We will keep you updated.
(APPSEC-2557)
Hi @pepdekpd ,
It's possible for you to provide more information regarding your problem? Our internal AppSec team was not able to reproduce the problem.
If you can provide us with a mock code sample with no sensitive information and also triggers the same problem as the original code sample, will help us a lot to fully understand the problem and provide you with the best information.
@pepdekpd thank you so much! Yes, the template you sent is enough for us to analyze!
Notice that i deleted your comment, so we make sure none of your code is shared online, for security purposes! I already have a copy on my local env, so we can work on it on our side. Hope this is okey for you! I will keep you updated.
Running Kics github action 2.0 on lambda with following environment variables:
Results in:
Expected Behavior
I do no think this is an issue, the variables (apiCredentials, progressMarker) point to names of systems manager parameter store parameters. The lambda retrieves the credentials values using the names of the parameters, it is not "Hardcoded AWS Access Key In Lambda", so the vulnerability should not be raised in this case.