What is CVE-2020-10673?A high-severity flaw in Jackson-Databind, explained.
CVE-2020-10673 is a high-severity flaw (CVSS 8.8) in Jackson-Databind from Fasterxml, published on 18 March 2020. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 8.0%. If you run an affected version, plan in the vendor’s fix.
Published 18 March 2020. Record last updated 3 July 2024. We keep this page's data up to date.
What is CVE-2020-10673? In plain terms.
It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.ResourceRef (aka caucho-quercus).
What kind of flaw is it?
- CWE-502Deserialization of Untrusted Data
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickYes, a person has to take an action
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Is CVE-2020-10673 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 8.0%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2020-10673 scores 53. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2020-10673 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2020-10673? 31 products.
The published record lists 31 products from 4 vendors. Versions are shown as published: "2.0.0 to before 2.6.7.4" means from 2.0.0 up to, but not including, 2.6.7.4. If you run one of these, check your version, then go to the fix below.
- Application
Jackson-Databind
by Fasterxml
Affected versions2.0.0 to before 2.6.7.42.9.0 to before 2.9.10.4 - Application
Banking Digital Experience
by Oracle
Affected versions18.118.218.319.119.220.1 - Application
Primavera Unifier
by Oracle
Affected versions16.116.217.7 to 17.1218.819.12 - Application
Retail Xstore Point of Service
by Oracle
Affected versions15.016.017.018.019.0 - Application
Financial Services Institutional Performance Analytics
by Oracle
Affected versions8.0.68.0.78.1.0 - Application
Retail Service Backbone
by Oracle
Affected versions14.115.016.0 - Application
Communications Contacts Server
by Oracle
Affected versions8.0.0.4.08.0.0.5.0 - Application
Communications Network Charging and Control
by Oracle
Affected versions6.0.112.0.0 to 12.0.3 - Application
Enterprise Manager Base Platform
by Oracle
Affected versions13.3.0.013.4.0.0
How do I fix CVE-2020-10673? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2020-10673 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to com.caucho.config.types.Resour...
- Matched to
- Jackson-Databind on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2020-10673 is a high-severity flaw in Jackson-Databind from Fasterxml, published on 18 March 2020. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.
It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2020-10673 is 53 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 8.0%. That can change at any time, which is why we keep watching.
For Jackson-Databind from Fasterxml: 2.0.0 to before 2.6.7.4, 2.9.0 to before 2.9.10.4. The record lists 31 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.