NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
285 matching advisories · page 4 of 10Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2020-19143 Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the "TIFFVGetField" funtion in the component 'libtiff/tif_dir.c'. simplesystems · libtiff, debian · debian_linux 2021-09-09 high7.5 CVE-2020-19131 Buffer Overflow in LibTiff v4.0.10 allows attackers to cause a denial of service via the "invertImage()" function in the component "tiffcrop". simplesystems · libtiff, debian · debian_linux 2021-09-07 high7.8 CVE-2020-35524 A heap-based buffer overflow flaw was found in libtiff in the handling of TIFF images in libtiff's TIFF2PDF tool. libtiff · libtiff, debian · debian_linux, fedoraproject · fedora +2 2021-03-09 high7.8 CVE-2020-35523 An integer overflow flaw was found in libtiff that exists in the tif_getimage.c file. libtiff · libtiff, debian · debian_linux, netapp · ontap_select_deploy_administration_utility +1 2021-03-09 medium5.5 CVE-2020-35522 In LibTIFF, there is a memory malloc failure in tif_pixarlog.c. libtiff · libtiff, netapp · ontap_select_deploy_administration_utility, fedoraproject · fedora +1 2021-03-09 medium5.5 CVE-2020-35521 A flaw was found in libtiff. libtiff · libtiff, redhat · enterprise_linux, fedoraproject · fedora +1 2021-03-09 high8.8 CVE-2020-35654 In Pillow before 8.1.0, TiffDecode has a heap-based buffer overflow when decoding crafted YCbCr files because of certain interpretation conflicts with LibTIFF … pip · Pillow 2021-01-12 medium6.5 CVE-2014-8128 LibTIFF prior to 4.0.4, as used in Apple iOS before 8.4 and OS X before 10.10.4 and other products, allows remote attackers to cause a denial of service (out-o… libtiff · libtiff 2020-02-12 high8.8 CVE-2019-17546 tif_getimage.c in LibTIFF through 4.0.10, as used in GDAL through 3.0.1 and other products, has an integer overflow that potentially causes a heap-based buffer… libtiff · libtiff, osgeo · gdal 2019-10-14 medium6.5 CVE-2019-14973 _TIFFCheckMalloc and _TIFFCheckRealloc in tif_aux.c in LibTIFF through 4.0.10 mishandle Integer Overflow checks because they rely on compiler behavior that is … libtiff · libtiff, debian · debian_linux, fedoraproject · fedora +1 2019-08-14 high7.5 CVE-2017-16232 LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c,… libtiff · libtiff, opensuse · leap, suse · linux_enterprise_desktop +2 2019-03-21 medium6.5 CVE-2019-7663 An Invalid Address dereference was discovered in TIFFWriteDirectoryTagTransferfunction in libtiff/tif_dirwrite.c in LibTIFF 4.0.10, affecting the cpSeparateBuf… libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux +1 2019-02-09 high8.8 CVE-2019-6128 The TIFFFdOpen function in tif_unix.c in LibTIFF 4.0.10 has a memory leak, as demonstrated by pal2rgb. libtiff · libtiff, canonical · ubuntu_linux, opensuse · leap +1 2019-01-11 medium6.5 CVE-2018-19210 In LibTIFF 4.0.9, there is a NULL pointer dereference in the TIFFWriteDirectorySec function in tif_dirwrite.c that will lead to a denial of service attack, as … libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux 2018-11-12 medium6.5 CVE-2018-18661 An issue was discovered in LibTIFF 4.0.9. libtiff · libtiff, canonical · ubuntu_linux 2018-10-26 high8.8 CVE-2018-18557 LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0alpha4, 4.0.0alpha5, 4.0.0alpha6, 4.0.0beta7, 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.4beta, 4.0.5, 4.0.6, 4.0.7… libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux 2018-10-22 high8.8 CVE-2018-17795 The function t2p_write_pdf in tiff2pdf.c in LibTIFF 4.0.9 and earlier allows remote attackers to cause a denial of service (heap-based buffer overflow and appl… libtiff · libtiff 2018-09-30 high8.8 CVE-2018-17101 An issue was discovered in LibTIFF 4.0.9. debian · debian_linux, libtiff · libtiff, canonical · ubuntu_linux 2018-09-16 high8.8 CVE-2018-17100 An issue was discovered in LibTIFF 4.0.9. debian · debian_linux, libtiff · libtiff, canonical · ubuntu_linux 2018-09-16 medium6.5 CVE-2018-17000 A NULL pointer dereference in the function _TIFFmemcmp at tif_unix.c (called from TIFFWriteDirectoryTagTransferfunction) in LibTIFF 4.0.9 allows an attacker to… libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux 2018-09-13 high8.8 CVE-2018-16335 newoffsets handling in ChopUpSingleUncompressedStrip in tif_dirread.c in LibTIFF 4.0.9 allows remote attackers to cause a denial of service (heap-based buffer … libtiff · libtiff, debian · debian_linux 2018-09-02 high8.8 CVE-2018-15209 ChopUpSingleUncompressedStrip in tif_dirread.c in LibTIFF 4.0.9 allows remote attackers to cause a denial of service (heap-based buffer overflow and applicatio… libtiff · libtiff, debian · debian_linux 2018-08-08 high8.8 CVE-2018-12900 Heap-based buffer overflow in the cpSeparateBufToContigBuf function in tiffcp.c in LibTIFF 3.9.3, 3.9.4, 3.9.5, 3.9.6, 3.9.7, 4.0.0beta7, 4.0.0alpha4, 4.0.0alp… libtiff · libtiff, canonical · ubuntu_linux 2018-06-26 medium6.5 CVE-2018-10963 The TIFFWriteDirectorySec() function in tif_dirwrite.c in LibTIFF through 4.0.9 allows remote attackers to cause a denial of service (assertion failure and app… libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux 2018-05-10 medium6.5 CVE-2018-10801 TIFFClientOpen in tif_unix.c in LibTIFF 3.8.2 has memory leaks, as demonstrated by bmp2tiff. libtiff · libtiff 2018-05-08 medium6.5 CVE-2018-10779 TIFFWriteScanline in tif_write.c in LibTIFF 3.8.2 has a heap-based buffer over-read, as demonstrated by bmp2tiff. libtiff · libtiff, canonical · ubuntu_linux 2018-05-07 medium6.5 CVE-2018-10126 ijg-libjpeg before 9d, as used in tiff2pdf (from LibTIFF) and other products, does not check for a NULL pointer at a certain place in jpeg_fdct_16x16 in jfdcti… libtiff · libtiff 2018-04-21 high8.8 CVE-2018-8905 In LibTIFF 4.0.9, a heap-based buffer overflow occurs in the function LZWDecodeCompat in tif_lzw.c via a crafted TIFF file, as demonstrated by tiff2ps. libtiff · libtiff, debian · debian_linux, canonical · ubuntu_linux +3 2018-03-22 high8.8 CVE-2016-5314 Buffer overflow in the PixarLogDecode function in tif_pixarlog.c in LibTIFF 4.0.6 and earlier allows remote attackers to cause a denial of service (application… libtiff · libtiff, opensuse · leap, opensuse · opensuse +2 2018-03-12 medium6.5 CVE-2014-8130 The _TIFFmalloc function in tif_unix.c in LibTIFF 4.0.3 does not reject a zero size, which allows remote attackers to cause a denial of service (divide-by-zero… libtiff · libtiff, redhat · enterprise_linux_desktop, redhat · enterprise_linux_server +6 2018-03-12

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.