Parsson vulnerabilitiesRanked by how likely they are to be used.
Parsson is made by Eclipse. We track 2 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Parsson, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Parsson vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Parsson's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Parsson flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 0.8%CVE-2023-4043High
In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from untrusted sources can lead malicious actors to exploit the fact that the built-in support for parsing numbers with large scale in Java has a...
- 0.6%CVE-2023-7272High
In Eclipse Parsson before 1.0.4 and 1.1.3, a document with a large depth of nested objects can allow an attacker to cause a Java stack overflow exception and denial of service.
Running Parsson? 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
In Eclipse Parsson before versions 1.1.4 and 1.0.5, Parsing JSON from untrusted sources can lead malicious actors to exploit the fact that the built-in support for parsing numbers with large scale in Java has a number of edge cases where the input text of a number can lead to much larger processing time than one would expect. To mitigate the risk, parsson put in place a size limit for the numbers as well as their scale.
- Matched to
- Parsson 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.
We track 2 published vulnerabilities listed under the name Parsson, across 12 versions.
None of Parsson's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Parsson. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.