NetSight

Security Dashboard

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

Reset
131 matching advisories · page 2 of 5Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2018-9018 In GraphicsMagick 1.3.28, there is a divide-by-zero in the ReadMNGImage function of coders/png.c. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-25 medium6.5 CVE-2017-18231 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 medium6.5 CVE-2017-18230 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 medium6.5 CVE-2017-18229 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-14 high8.8 CVE-2017-18220 The ReadOneJNGImage and ReadJNGImage functions in coders/png.c in GraphicsMagick 1.3.26 allow remote attackers to cause a denial of service (magick/blob.c Clos… graphicsmagick · graphicsmagick 2018-03-05 medium6.5 CVE-2017-18219 An issue was discovered in GraphicsMagick 1.3.26. graphicsmagick · graphicsmagick, debian · debian_linux 2018-03-05 high8.8 CVE-2018-6799 The AcquireCacheNexus function in magick/pixel_cache.c in GraphicsMagick before 1.3.28 allows remote attackers to cause a denial of service (heap overwrite) or… graphicsmagick · graphicsmagick, debian · debian_linux 2018-02-07 medium6.5 CVE-2018-5685 In GraphicsMagick 1.3.27, there is an infinite loop and application hang in the ReadBMPImage function (coders/bmp.c). graphicsmagick · graphicsmagick, debian · debian_linux 2018-01-14 high8.8 CVE-2018-5360 LibTIFF before 4.0.6 mishandles the reading of TIFF files, as demonstrated by a heap-based buffer over-read in the ReadTIFFImage function in coders/tiff.c in G… libtiff · libtiff, graphicsmagick · graphicsmagick 2018-01-14 high8.8 CVE-2017-17915 In GraphicsMagick 1.4 snapshot-20171217 Q8, there is a heap-based buffer over-read in ReadMNGImage in coders/png.c, related to accessing one byte before testin… graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-27 high8.8 CVE-2017-17913 In GraphicsMagick 1.4 snapshot-20171217 Q8, there is a stack-based buffer over-read in WriteWEBPImage in coders/webp.c, related to an incompatibility with libw… graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-27 high8.8 CVE-2017-17912 In GraphicsMagick 1.4 snapshot-20171217 Q8, there is a heap-based buffer over-read in ReadNewsProfile in coders/tiff.c, in which LocaleNCompare reads heap data… graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-27 high7.5 CVE-2017-17783 In GraphicsMagick 1.3.27a, there is a buffer over-read in ReadPALMImage in coders/palm.c when QuantumDepth is 8. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-20 high8.8 CVE-2017-17782 In GraphicsMagick 1.3.27a, there is a heap-based buffer over-read in ReadOneJNGImage in coders/png.c, related to oFFs chunk allocation. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-20 high8.8 CVE-2017-17503 ReadGRAYImage in coders/gray.c in GraphicsMagick 1.3.26 has a magick/import.c ImportGrayQuantumType heap-based buffer over-read via a crafted file. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-11 high8.8 CVE-2017-17502 ReadCMYKImage in coders/cmyk.c in GraphicsMagick 1.3.26 has a magick/import.c ImportCMYKQuantumType heap-based buffer over-read via a crafted file. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-11 high8.8 CVE-2017-17501 WriteOnePNGImage in coders/png.c in GraphicsMagick 1.3.26 has a heap-based buffer over-read via a crafted file. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-11 high8.8 CVE-2017-17500 ReadRGBImage in coders/rgb.c in GraphicsMagick 1.3.26 has a magick/import.c ImportRGBQuantumType heap-based buffer over-read via a crafted file. graphicsmagick · graphicsmagick, debian · debian_linux 2017-12-11 high8.8 CVE-2017-17498 WritePNMImage in coders/pnm.c in GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (bit_stream.c MagickBitStreamMSBWrite heap-based bu… graphicsmagick · graphicsmagick 2017-12-11 high8.8 CVE-2017-16669 coders/wpg.c in GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (heap-based buffer overflow and application crash) or possibly have … graphicsmagick · graphicsmagick, debian · debian_linux 2017-11-09 high8.8 CVE-2017-16547 The DrawImage function in magick/render.c in GraphicsMagick 1.3.26 does not properly look for pop keywords that are associated with push keywords, which allows… graphicsmagick · graphicsmagick 2017-11-06 high8.8 CVE-2017-16545 The ReadWPGImage function in coders/wpg.c in GraphicsMagick 1.3.26 does not properly validate colormapped images, which allows remote attackers to cause a deni… graphicsmagick · graphicsmagick 2017-11-05 medium6.5 CVE-2017-16353 GraphicsMagick 1.3.26 is vulnerable to a memory information disclosure vulnerability found in the DescribeImage function of the magick/describe.c file, because… graphicsmagick · graphicsmagick, debian · debian_linux 2017-11-01 high8.8 CVE-2017-16352 GraphicsMagick 1.3.26 is vulnerable to a heap-based buffer overflow vulnerability found in the "Display visual image directory" feature of the DescribeImage() … graphicsmagick · graphicsmagick, debian · debian_linux 2017-11-01 high8.8 CVE-2017-15930 In ReadOneJNGImage in coders/png.c in GraphicsMagick 1.3.26, a Null Pointer Dereference occurs while transferring JPEG scanlines, related to a PixelPacket poin… graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-27 medium6.5 CVE-2017-15277 ReadGIFImage in coders/gif.c in ImageMagick 7.0.6-1 and GraphicsMagick 1.3.26 leaves the palette uninitialized when processing a GIF file that has neither a gl… graphicsmagick · graphicsmagick, imagemagick · imagemagick 2017-10-12 high8.8 CVE-2017-15238 ReadOneJNGImage in coders/png.c in GraphicsMagick 1.3.26 has a use-after-free issue when the height or width is zero, related to ReadJNGImage. graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-11 medium6.5 CVE-2017-14997 GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (excessive memory allocation) because of an integer underflow in ReadPICTImage in co… graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-04 medium6.5 CVE-2017-14994 ReadDCMImage in coders/dcm.c in GraphicsMagick 1.3.26 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted DICOM image… graphicsmagick · graphicsmagick, debian · debian_linux 2017-10-04 medium6.5 CVE-2017-14733 ReadRLEImage in coders/rle.c in GraphicsMagick 1.3.26 mishandles RLE headers that specify too few colors, which allows remote attackers to cause a denial of se… graphicsmagick · graphicsmagick, debian · debian_linux 2017-09-25

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.