HIGH vulnerability: bump itextpdf from 5.5.3 to 5.5.12 #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Vulnerability Information
Bumps itextpdf from 5.5.3 to 5.5.12.
Listed dependency com.itextpdf:itextpdf contains vulnerable methods which are called from this project. This vulnerability appears to affect itextpdf package versions lower than 5.5.12 (excluding). The vulnerability can be fixed by updating the version to 5.5.12, as can be seen from the description here.
Vulnerable method calls
What do the columns represent?
The 1st column in the table indicates the method in this repository that was found to be affected
by vulnerable methods from the itextpdf package.
The 2nd column indicates the itextpdf method that was directly called from this repository.
The 3rd column indicates the origin vulnerable method in the itextpdf package. According to our dataset, this is one of the methods that produces the CVE-2017-9096 vulnerability. This method was found to be internally chain-called in the itextpdf package by the method listed in column 2.
How were the results generated?
This vulnerability was analyzed specifically for usage in this project using the FASTEN Project. Statical method-level analysis was used to check for usage of vulnerable methods in the project.
Method calls between your project and itextpdf have been mapped using a directed graph. From this graph, it could be then be seen whether any vulnerable itextpdf methods are being called from within your project.
Research Scope
We are a team of 3 BSc Computer Science students at the TU Delft. Our goal is to conduct research on how developers react to method-level vulnerability information that affects their projects. We would highly appreciate if you could help us with our research and please tick statements which apply to you below.
First impression checklist
After fixing vulnerability checklist