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.

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

Snyk and Trivy reports two vulnerabilities in the CXF version Oxalis-AS4 uses #198

Closed
post-svejk opened this issue Dec 20, 2022 · 1 comment

Comments

@post-svejk
Copy link

See for example:

Sven-Jrgens-MacBook-Pro:Oxalis-AS4 svejk$ snyk test

Testing /Users/svejk/src/Oxalis-AS4...

Tested 80 dependencies for known issues, found 4 issues, 4 vulnerable paths.


Issues to fix by upgrading:

  Upgrade org.apache.cxf:[email protected] to org.apache.cxf:[email protected] to fix
  ✗ Server-side Request Forgery (SSRF) (new) [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-ORGAPACHECXF-3168315] in org.apache.cxf:[email protected]
    introduced by org.apache.cxf:[email protected]

  Upgrade org.apache.cxf:[email protected] to org.apache.cxf:[email protected] to fix
  ✗ Information Exposure (new) [High Severity][https://security.snyk.io/vuln/SNYK-JAVA-ORGAPACHECXF-3168313] in org.apache.cxf:[email protected]
    introduced by org.apache.cxf:[email protected]

  Upgrade org.apache.wss4j:[email protected] to org.apache.wss4j:[email protected] to fix
  ✗ Denial of Service (DoS) [Medium Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLWOODSTOX-3091135] in com.fasterxml.woodstox:[email protected]
    introduced by org.apache.wss4j:[email protected] > org.apache.santuario:[email protected] > com.fasterxml.woodstox:[email protected]
  ✗ XML External Entity (XXE) Injection [Critical Severity][https://security.snyk.io/vuln/SNYK-JAVA-COMFASTERXMLWOODSTOX-2928754] in com.fasterxml.woodstox:[email protected]
    introduced by org.apache.wss4j:[email protected] > org.apache.santuario:[email protected] > com.fasterxml.woodstox:[email protected]

I made a draft attempt to solve the issues by upgrading CXF and WSS4J. See the PR:
#197

@post-svejk
Copy link
Author

Thanks for the quick response, @aaron-kumar! Dealing with the signature algorithm was really what I was missing in my draft PR, so it is no longer needed. However, I ran into new signature algorithm problems when testing this release. See next issue.

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

No branches or pull requests

1 participant