Pspp vulnerabilitiesRanked by how likely they are to be used.
Pspp is made by Gnu. We track 15 published vulnerabilities in it, across 36 versions. None of them is on the list of flaws known to be exploited today. If you run Pspp, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Pspp vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pspp's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pspp 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.
- 2.0%CVE-2019-9211Medium
There is a reachable assertion abort in the function write_long_string_missing_values() in data/sys-file-writer.c in libdata.a in GNU PSPP 1.2.0 that will lead to denial of service.
- 1.6%CVE-2017-10791Medium
There is an Integer overflow in the hash_int function of the libpspp library in GNU PSPP before 0.11.0.
- 1.6%CVE-2017-10792Medium
There is a NULL Pointer Dereference in the function ll_insert() of the libpspp library in GNU PSPP before 0.11.0.
- 1.3%CVE-2017-12958High
There is an illegal address access in the function output_hex() in data/data-out.c of the libpspp library in GNU PSPP before 1.0.1 that will lead to remote denial of service.
- 1.3%CVE-2017-12959High
There is a reachable assertion abort in the function dict_add_mrset() in data/dictionary.c of the libpspp library in GNU PSPP before 1.0.1 that will lead to a remote denial of service attack.
- 1.3%CVE-2017-12960High
There is a reachable assertion abort in the function dict_rename_var() in data/dictionary.c of the libpspp library in GNU PSPP before 1.0.1 that will lead to remote denial of service.
- 1.3%CVE-2017-12961High
There is an assertion abort in the function parse_attributes() in data/sys-file-reader.c of the libpspp library in GNU PSPP before 1.0.1 that will lead to remote denial of service.
- 0.8%CVE-2018-20230High
An issue was discovered in PSPP 1.2.0. There is a heap-based buffer overflow at the function read_bytes_internal in utilities/pspp-dump-sav.c, which allows attackers to cause a denial of service (application crash)...
- 0.5%CVE-2022-39831High
An issue was discovered in PSPP 1.6.2. There is a heap-based buffer overflow at the function read_bytes_internal in utilities/pspp-dump-sav.c, which allows attackers to cause a denial of service (application crash)...
- 0.5%CVE-2022-39832High
An issue was discovered in PSPP 1.6.2. There is a heap-based buffer overflow at the function read_string in utilities/pspp-dump-sav.c, which allows attackers to cause a denial of service (application crash) or...
Running Pspp? 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
There is a reachable assertion abort in the function write_long_string_missing_values() in data/sys-file-writer.c in libdata.a in GNU PSPP 1.2.0 that will lead to denial of service.
- Matched to
- Pspp 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 15 published vulnerabilities listed under the name Pspp, across 36 versions.
None of Pspp's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Pspp. 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.