Skip to content

[Snyk] Fix for 1 vulnerabilities - #10

Open
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-3733457c4129030502a6b9ba0b4412b0
Open

[Snyk] Fix for 1 vulnerabilities#10
snyk-bot wants to merge 1 commit into
masterfrom
snyk-fix-3733457c4129030502a6b9ba0b4412b0

Conversation

@snyk-bot

Copy link
Copy Markdown
Contributor

Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • pom.xml

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Upgrade Breaking Change Exploit Maturity Reachability
medium severity 495/1000
Why? Recently disclosed, Has a fix available, CVSS 5.9
Denial of Service (DoS)
SNYK-JAVA-COMFASTERXMLJACKSONCORE-2326698
io.gatling.highcharts:gatling-charts-highcharts:
3.7.0 -> 3.7.3
io.gatling:gatling-app:
3.7.0 -> 3.7.3
io.gatling:gatling-recorder:
3.7.0 -> 3.7.3
No No Known Exploit No Path Found

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

@RhysBushnell
RhysBushnell force-pushed the snyk-fix-3733457c4129030502a6b9ba0b4412b0 branch from f456307 to e4d782b Compare June 12, 2026 12:35
@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedio.gatling/​gatling-app@​3.7.0 ⏵ 3.7.33610090100100
Updatedio.gatling/​gatling-recorder@​3.7.0 ⏵ 3.7.33610090100100
Updatedio.gatling.highcharts/​gatling-charts-highcharts@​3.7.0 ⏵ 3.7.39810010010080

View full report

@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: maven ch.qos.logback:logback-core is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pom.xmlmaven/io.gatling/gatling-app@3.7.3maven/ch.qos.logback/logback-core@1.2.9

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/ch.qos.logback/logback-core@1.2.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: maven ch.qos.logback:logback-core is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pom.xmlmaven/io.gatling/gatling-app@3.7.3maven/ch.qos.logback/logback-core@1.2.9

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/ch.qos.logback/logback-core@1.2.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: maven io.netty:netty-codec is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pom.xmlmaven/io.gatling/gatling-recorder@3.7.3maven/io.netty/netty-codec@4.1.72.Final

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/io.netty/netty-codec@4.1.72.Final. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: maven io.netty:netty-codec is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pom.xmlmaven/io.gatling/gatling-recorder@3.7.3maven/io.netty/netty-codec@4.1.72.Final

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/io.netty/netty-codec@4.1.72.Final. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: maven io.netty:netty-codec is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pom.xmlmaven/io.gatling/gatling-recorder@3.7.3maven/io.netty/netty-codec@4.1.72.Final

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore maven/io.netty/netty-codec@4.1.72.Final. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant