Swi-Prolog vulnerabilitiesNone on the known-exploited list.
Swi-Prolog has 4 published vulnerabilities across 1 product in our catalogue. None of them is on the list of flaws known to be exploited today. The most affected product is Swi-Prolog, with 4. If you run Swi-Prolog software, patch the exploited flaws first.
We keep watching the known-exploited list.
Which Swi-Prolog products have the most vulnerabilities?
Swi-Prolog leads with 4 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.
Which Swi-Prolog vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Swi-Prolog's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Swi-Prolog 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.
- 12%CVE-2011-2896Medium
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in...
- 4.0%CVE-2012-6089High
Multiple stack-based buffer overflows in the canoniseFileName function in os/pl-os.c in SWI-Prolog before 6.2.5 and 6.3.x before 6.3.7 allow remote attackers to cause a denial of service (application crash) or...
- 3.1%CVE-2012-6090High
Multiple stack-based buffer overflows in the expand function in os/pl-glob.c in SWI-Prolog before 6.2.5 and 6.3.x before 6.3.7 allow remote attackers to cause a denial of service (application crash) or possibly...
- 1.2%CVE-2017-17524High
library/www_browser.pl in SWI-Prolog 7.2.3 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection...
All Swi-Prolog products we track.
1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.
Running Swi-Prolog? 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
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and other products, does not properly handle code words that are absent from the decompression table when encountered, which allows remote attackers to trigger an infinite loop or a heap-based buffer overflow, and possibly execute arbitrary code, via a crafted compressed stream, a related issue to CVE-2006-1168 and CVE-2011-2895.
- Matched to
- Swi-Prolog 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.
Our catalogue lists 4 published vulnerabilities across 1 product and 497 versions from Swi-Prolog.
None of Swi-Prolog's vulnerabilities is on the list of flaws known to be exploited today.
Swi-Prolog, with 4 published vulnerabilities. Its own page lists the ones known to be exploited.
Create a Precursor Intelligence account and track the Swi-Prolog products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.