alibaba / alibaba/Sentinel

Potential Vulnerabilities Due To Hidden Dependencies

Open
#3,641 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
23.1k
Forks
8.1k
PR merge metrics
No merged PRs in 30d

Description

I am a student at Paderborn University and am analyzing security risks introduced by hidden dependencies in my master’s thesis. Software security researchers and I have found that this GitHub project incorporates known vulnerabilities within modified dependencies.

What are Hidden Dependencies?
Dependency modifications such as re-bundling and re-packaging (introduced for example by the Maven Shade plugin) can hide the inclusion of potentially vulnerable dependencies, as those dependencies are not found by vulnerability scanners that rely on metadata. In our approach, we identified hidden dependencies by matching fingerprints of known-to-be-vulnerable dependencies to the JAR files of direct and transitive dependencies listed in the software bill of materials.

Suggested Solution
You can find a list of hidden vulnerable dependencies that are included in this project at the end of this message. Please note that exploitability has not been investigated. We recommend either removing the affected dependencies or updating them to newer versions.

Your Perspective
As part of my master’s thesis, I am investigating awareness and patching behavior related to such hidden vulnerable dependencies. I would appreciate it if you could share your perspective and take a 5-minute anonymous survey at: https://umfragen.uni-paderborn.de/index.php/542735. Thank you!

*******************
List of vulnerable modified dependencies:

org.apache.tomcat.embed:tomcat-embed-core:9.0.60 includes:
- org.apache.tomcat:tomcat-catalina:9.0.60 - CVE-2023-28708, CVE-2024-52316, CVE-2025-55668
- org.apache.tomcat:tomcat-util:9.0.60 - CVE-2024-38286, CVE-2025-52434
- org.apache.tomcat:tomcat-util:9.0.59 - CVE-2024-38286, CVE-2025-52434

io.quarkus:quarkus-ide-launcher:1.4.1.Final includes:
- commons-io:commons-io:2.6 - CVE-2021-29425, CVE-2024-47554
- org.apache.commons:commons-lang3:3.9 - CVE-2025-48924
- org.apache.httpcomponents:httpclient:4.5.12 - CVE-2020-13956
- org.apache.maven:maven-core:3.6.3 - CVE-2021-26291
- org.apache.maven.shared:maven-shared-utils:3.2.1 - CVE-2022-29599
- org.codehaus.plexus:plexus-utils:3.2.1 - CVE-2025-67030
- org.jsoup:jsoup:1.11.3 - CVE-2021-37714, CVE-2022-36033
- com.google.guava:guava:27.0-jre - CVE-2020-8908, CVE-2023-2976

org.apache.tomcat.embed:tomcat-embed-core:9.0.46 includes:
- org.apache.tomcat:tomcat-catalina:9.0.46 - CVE-2023-28708, CVE-2024-52316, CVE-2025-55668
- org.apache.tomcat:tomcat-util:9.0.46 - CVE-2024-38286, CVE-2025-52434
- org.apache.tomcat:tomcat-util:9.0.46 - CVE-2024-38286, CVE-2025-52434

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the software bill of materials and the listed modified JAR artifacts, including the Tomcat and Quarkus dependencies and their reported CVEs. Confirm which vulnerable dependencies are included and whether they can be removed or updated; done means the affected versions are addressed and the resulting dependency set is checked again.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.