CRITICAL vulnerability: bump jackson-databind from 2.7.9.4 to 2.9.9.2

[MethodLevelAnalyzer]

Vulnerability Information

Bumps jackson-databind from 2.7.9.4 to 2.9.9.2.

Listed dependency com.fasterxml.jackson.core:jackson-databind contains vulnerable methods which are called from this project. This vulnerability appears to affect jackson-databind package versions lower than 2.9.9.2 (excluding). The vulnerability has been fixed in version 2.9.9.2, as can be seen from the linked CVE or package release notes -
the micro-patch of 2.9.9.2 refers to the fix of this vulnerability.

Property	Value
Linked CVE	CVE-2019-14379
Number of affected methods	1
Severity	CRITICAL
Current version	2.7.9.4
Updated version	2.9.9.2
Backwards Compatibility	True

Vulnerable method calls

Methods in this repository	Used package methods	Origin vulnerable method
io.termd.core.http/ HttpTtyConnection.writeToDecoder(String msg)	com.fasterxml.jackson.databind/ ObjectMapper.readValue(String content, Class valueType)	com.fasterxml.jackson.databind.deser.std/ EnumSetDeserializer(JavaType enumType, JsonDeserializer<?> deser)
io.termd.core.http/ HttpTtyConnection.writeToDecoder(String msg)	com.fasterxml.jackson.databind/ ObjectMapper.readValue(String content, Class valueType)	com.fasterxml.jackson.databind.deser/ BasicDeserializerFactory.createMapDeserializer(DeserializationContext ctxt, MapType type, BeanDescription beanDesc)

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 jackson-databind package.

The 2nd column indicates the jackson-databind method that was directly called from this repository.

The 3rd column indicates the origin vulnerable method in the jackson-databind package. According to our dataset, this is one of the methods that produces the CVE-2019-14379 vulnerability. This method was found to be internally chain-called in the jackson-databind 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 jackson-databind have been mapped using a directed graph. From this graph, it could be then be seen whether any vulnerable jackson-databind 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

• I have read this pull request description.
• I was aware of this dependency vulnerability affecting my project before being informed by this Pull Request.
• I was convinced by the provided method information that this vulnerability indeed affects my project.
• After seeing the provided method-level information, I plan on fixing the vulnerability.

After fixing vulnerability checklist

• I found that the provided method information has made my process of dealing with the vulnerable dependency easier.
• I have given priority to the task of fixing the vulnerability over other project tasks that are yet to be completed.
• I would like to receive this kind of method information in future vulnerable dependency Pull Request descriptions.