Skip to content

Conversation

@baardl
Copy link
Contributor

@baardl baardl commented Nov 2, 2024

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the maven dependencies of this project.

Snyk changed the following file(s):

  • pom.xml

Vulnerabilities that will be fixed with an upgrade:

Issue Score Upgrade
low severity Information Disclosure
SNYK-JAVA-COMGOOGLEGUAVA-1015415
  486   com.fasterxml.jackson.datatype:jackson-datatype-guava:
2.14.1 -> 2.17.3
Proof of Concept
low severity Creation of Temporary File in Directory with Insecure Permissions
SNYK-JAVA-COMGOOGLEGUAVA-5710356
  379   com.fasterxml.jackson.datatype:jackson-datatype-guava:
2.14.1 -> 2.17.3
No Known Exploit

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Creation of Temporary File in Directory with Insecure Permissions

@socket-security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert Package NoteSourceCI
Critical CVE maven/dom4j/dom4j@1.6.1 ⚠︎
Critical CVE maven/org.apache.axis/axis@1.4 ⚠︎
Critical CVE maven/commons-fileupload/commons-fileupload@1.2 ⚠︎
Critical CVE maven/com.thoughtworks.xstream/xstream@1.2.2 ⚠︎
Critical CVE maven/com.thoughtworks.xstream/xstream@1.2.2 ⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore maven/dom4j/dom4j@1.6.1
  • @SocketSecurity ignore maven/org.apache.axis/axis@1.4
  • @SocketSecurity ignore maven/commons-fileupload/commons-fileupload@1.2
  • @SocketSecurity ignore maven/com.thoughtworks.xstream/xstream@1.2.2

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.

3 participants