Dependency on Vulnerable Third-Party Component
The product uses a third-party component that contains one or more known vulnerabilities.
Using vulnerable dependencies exposes the application to known exploits. Container images and application dependencies should be regularly scanned and updated.
How to fix this vulnerability
Prevention strategies for Dependency on Vulnerable Third-Party based on 3 Shoulder detection rules.
Clean apt cache in the same RUN layer to reduce image size
FROM ubuntu:22.04 - RUN apt-get update && apt-get install -y --no-install-recommends curl + RUN apt-get update && \ + apt-get install -y --no-install-recommends curl && \ + rm -rf /var/lib/apt/lists/*
Add --no-install-recommends to apt-get install to minimize image size
FROM ubuntu:22.04 - RUN apt-get update && apt-get install -y curl + RUN apt-get update && apt-get install -y --no-install-recommends curl
Add -y flag to apt-get install for non-interactive Docker builds
FROM ubuntu:22.04 - RUN apt-get update && apt-get install curl + RUN apt-get update && apt-get install -y curl
Find vulnerabilities in your code
Use Shoulder to scan your codebase for Dependency on Vulnerable Third-Party Component patterns. 3 rules.
# Scan with Shoulder CLI npx @shoulderdev/cli trust --cwe=1395 # Or scan entire project npx @shoulderdev/cli trust .
Detection Rules (3)
What to watch for in code reviews
These patterns indicate potential Dependency on Vulnerable Third-Party Component vulnerabilities. Look for these during code reviews and security audits.
Scan your codebase for Dependency on Vulnerable Third-Party Component
Shoulder CLI finds vulnerable patterns across your entire codebase.