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

Dependencies causes CVEs in your execution path #87

Open
CleWang opened this issue Mar 1, 2020 · 0 comments
Open

Dependencies causes CVEs in your execution path #87

CleWang opened this issue Mar 1, 2020 · 0 comments

Comments

@CleWang
Copy link

CleWang commented Mar 1, 2020

I found you are using a dependency with CVE. I found the buggy methods of the CVE in the program execution path of your project. To prevent potential security risks it may cause, I suggest a version update. Here is the detailed information:

  • Vulnerable Dependency: org.apache.uima : uimaj-core : 2.6.0

  • Call Chain to Buggy Methods:

    • Some files in your project call the library method org.apache.uima.cas.impl.XmiCasDeserializer.deserialize(java.io.InputStream,org.apache.uima.cas.CAS), which can reach the buggy method of CVE-2017-15691.

      • Files in your project:
        src/main/java/cz/brmlab/yodaqa/pipeline/AnswerHitlistDeserialize.java
      • One of the possible call chain:
      org.apache.uima.cas.impl.XmiCasDeserializer.deserialize(java.io.InputStream,org.apache.uima.cas.CAS)
      org.apache.uima.cas.impl.XmiCasDeserializer.deserialize(java.io.InputStream,org.apache.uima.cas.CAS,boolean,org.apache.uima.cas.impl.XmiSerializationSharedData,int) [buggy method]
      
  • Update suggestion: version 2.10.4
    2.10.4 is a safe version without CVEs. From 2.6.0 to 2.10.4, 31 of the APIs (called by 115 times in your project) were modified.

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