Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps-dev): bump org.apache.logging.log4j:log4j-jcl from 2.19.0 to 2.24.0 in /jans-auth-server #9421

Closed
wants to merge 1 commit into from

chore(deps-dev): bump org.apache.logging.log4j:log4j-jcl

188bef9
Select commit
Loading
Failed to load commit list.
Closed

chore(deps-dev): bump org.apache.logging.log4j:log4j-jcl from 2.19.0 to 2.24.0 in /jans-auth-server #9421

chore(deps-dev): bump org.apache.logging.log4j:log4j-jcl
188bef9
Select commit
Loading
Failed to load commit list.
DryRunSecurity / Sensitive Files Analyzer succeeded Sep 17, 2024 in 1s

DryRun Security

Details

Sensitive Files Analyzer Findings: 1 detected

⚠️ Potential Sensitive File jans-auth-server/agama/engine/pom.xml (click for details)
Type Potential Sensitive File
Description Java applications manage their dependencies through their pom.xml. A change in this file may indicate an addition of a library/dependency which could introduce additional risk to the application either through vulnerable code, expansion of the application's attack surface via additional routes, or malicious code.
Filename jans-auth-server/agama/engine/pom.xml
CodeLink

jans/jans-auth-server/agama/engine/pom.xml

Lines 242 to 248 in 188bef9

<dependency>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-jcl</artifactId>
<version>2.24.0</version>
<scope>test</scope>
</dependency>
View more details on DryRunSecurity