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
Copy file name to clipboardExpand all lines: DEPENDENCY_ANALYSIS.md
+38-3Lines changed: 38 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,9 +2,9 @@
2
2
3
3
## Vulnerable Dependency in Multiple Paths
4
4
5
-
This project demonstrates a vulnerable dependency (`commons-collections:3.2.1`) appearing in multiple paths in the dependency graph.
5
+
This project demonstrates vulnerable dependencies that appear in multiple dependency graph paths, along with additional vulnerable packages that have their own transitive dependencies.
@@ -69,7 +100,11 @@ In real-world scenarios, vulnerable dependencies often appear in multiple paths
69
100
- Harder to remediate (requires updating multiple parent dependencies)
70
101
- More likely to be overlooked by basic security scanning
71
102
72
-
This repository intentionally includes this pattern to demonstrate how dependency scanning tools like GitHub's Dependabot and CodeQL can detect such vulnerabilities across the entire dependency graph.
103
+
This repository intentionally includes this pattern to demonstrate how dependency scanning tools like GitHub's Dependabot and CodeQL can detect such vulnerabilities across the entire dependency graph. By including multiple vulnerable packages with their own transitive dependencies, the repository also demonstrates:
104
+
- How vulnerabilities cascade through dependency chains
105
+
- The importance of Software Composition Analysis (SCA)
106
+
- How GitHub's dependency graph visualizes these complex relationships
107
+
- The "..." ellipsis menu that appears in GitHub's UI when packages have additional information, vulnerabilities, or multiple dependency paths. This menu provides access to vulnerability details, remediation suggestions, and dependency path information.
Copy file name to clipboardExpand all lines: README.md
+9-4Lines changed: 9 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,10 +24,15 @@ This application contains the following types of security vulnerabilities:
24
24
4.**LDAP Injection** - Unescaped user input in LDAP filters
25
25
5.**Weak Cryptography** - Use of MD5 and weak random number generation
26
26
6.**Hard-coded Secrets** - Embedded credentials and encryption keys
27
-
7.**Vulnerable Dependencies** - Uses `commons-collections:3.2.1` which has known deserialization vulnerabilities (CVE-2015-7501). This dependency appears in multiple paths in the dependency graph:
28
-
- As a direct dependency
29
-
- As a transitive dependency through `commons-beanutils:1.9.2`
30
-
- As a transitive dependency through `commons-digester:2.1` → `commons-beanutils:1.8.3`
27
+
7.**Vulnerable Dependencies** - Multiple packages with known vulnerabilities:
28
+
-`commons-collections:3.2.1` - Deserialization vulnerabilities (CVE-2015-7501), appears in multiple paths:
29
+
- As a direct dependency
30
+
- As a transitive dependency through `commons-beanutils:1.9.2`
31
+
- As a transitive dependency through `commons-digester:2.1` → `commons-beanutils:1.8.3`
0 commit comments