The latest articles on DEV Community by Muhammad Nadeem (@muhammad-nadeem). https://dev.to/muhammad-nadeem https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4035722%2F1192293e-9bfa-435a-9278-83d400b1298a.jpg https://dev.to/muhammad-nadeem en Muhammad Nadeem Mon, 20 Jul 2026 19:10:27 +0000 https://dev.to/muhammad-nadeem/scanning-aws-lambda-for-vulnerabilities-with-amazon-inspector-305m https://dev.to/muhammad-nadeem/scanning-aws-lambda-for-vulnerabilities-with-amazon-inspector-305m <p>Recently completed a hands-on lab on using <strong>Amazon Inspector</strong> to scan AWS Lambda functions for vulnerabilities — here's a quick summary.</p> <h2> The Scenario </h2> <p>A team is building a new application using AWS Lambda and needs an automated way to catch vulnerabilities — not just in dependencies, but within the code itself, right after every deployment.</p> <h2> What I Did </h2> <p><strong>1. Activated Amazon Inspector</strong></p> <ul> <li>Navigated to Amazon Inspector in the AWS Console</li> <li>Activated the service for the account, which automatically enabled scanning for EC2, ECR, and AWS Lambda</li> <li>Waited until the dashboard showed Lambda function coverage at 100%</li> </ul> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F16v0sqhvlpge6ls6egm3.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F16v0sqhvlpge6ls6egm3.png" alt=" " width="800" height="450"></a></p> <p><strong>2. Reviewed the Findings</strong></p> <ul> <li>Opened "All findings" and found three vulnerabilities reported at Medium severity</li> <li>Selected the finding <strong>CVE-2023-32681 - requests</strong> </li> <li>Checked the Vulnerability details, including a link to the National Vulnerability Database (NVD) for more context</li> <li>Reviewed the Remediation section, which flagged the <code>requests</code> package as outdated and recommended an upgrade</li> </ul> <p><a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fus0sx5tajehn6afkklvn.png" class="article-body-image-wrapper"><img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fus0sx5tajehn6afkklvn.png" alt=" " width="800" height="450"></a></p> <p><strong>3. Remediated the Vulnerability</strong></p> <ul> <li>Opened the affected Lambda function (<code>get-request</code>) in the Lambda console</li> <li>Edited the <code>requirements.txt</code> file, removing the pinned version (<code>requests==2.20.0</code>) so it just read <code>requests</code> — ensuring the latest secure version installs automatically</li> <li>Deployed the updated function</li> </ul> devops aws claude lambda