NetSight

Security Dashboard

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

Reset
993 matching advisories · page 19 of 34Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2017-18251 An issue was discovered in ImageMagick 7.0.7. imagemagick · imagemagick, canonical · ubuntu_linux 2018-03-27 medium6.5 CVE-2017-18250 An issue was discovered in ImageMagick 7.0.7. imagemagick · imagemagick 2018-03-27 high8.8 CVE-2018-8960 The ReadTIFFImage function in coders/tiff.c in ImageMagick 7.0.7-26 Q16 does not properly restrict memory allocation, leading to a heap-based buffer over-read. imagemagick · imagemagick, canonical · ubuntu_linux 2018-03-23 high8.8 CVE-2018-8804 WriteEPTImage in coders/ept.c in ImageMagick 7.0.7-25 Q16 allows remote attackers to cause a denial of service (MagickCore/memory.c double free and application… imagemagick · imagemagick, canonical · ubuntu_linux 2018-03-20 critical9.8 CVE-2017-18211 In ImageMagick 7.0.7, a NULL pointer dereference vulnerability was found in the function saveBinaryCLProgram in magick/opencl.c because a program-lookup result… imagemagick · imagemagick, canonical · ubuntu_linux 2018-03-01 critical9.8 CVE-2017-18210 In ImageMagick 7.0.7, a NULL pointer dereference vulnerability was found in the function BenchmarkOpenCLDevices in MagickCore/opencl.c because a memory allocat… imagemagick · imagemagick 2018-03-01 high8.8 CVE-2017-18209 In the GetOpenCLCachedFilesDirectory function in magick/opencl.c in ImageMagick 7.0.7, a NULL pointer dereference vulnerability occurs because a memory allocat… imagemagick · imagemagick, canonical · ubuntu_linux 2018-03-01 medium6.5 CVE-2018-7470 An issue was discovered in ImageMagick 7.0.7-22 Q16. imagemagick · imagemagick 2018-02-25 medium6.5 CVE-2018-7443 The ReadTIFFImage function in coders/tiff.c in ImageMagick 7.0.7-23 Q16 does not properly validate the amount of image data in a file, which allows remote atta… imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux 2018-02-23 medium6.5 CVE-2018-6930 A stack-based buffer over-read in the ComputeResizeImage function in the MagickCore/accelerate.c file of ImageMagick 7.0.7-22 allows a remote attacker to cause… imagemagick · imagemagick 2018-02-13 medium6.5 CVE-2018-6876 The OLEProperty class in ole/oleprop.cpp in libfpx 1.3.1-10, as used in ImageMagick 7.0.7-22 Q16 and other products, allows remote attackers to cause a denial … imagemagick · imagemagick, libfpx_project · libfpx 2018-02-09 medium6.5 CVE-2018-6405 In the ReadDCMImage function in coders/dcm.c in ImageMagick before 7.0.7-23, each redmap, greenmap, and bluemap variable can be overwritten by a new pointer. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-30 medium6.5 CVE-2017-18029 In ImageMagick 7.0.6-10 Q16, a memory leak vulnerability was found in the function ReadMATImage in coders/mat.c, which allow remote attackers to cause a denial… imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-12 medium6.5 CVE-2017-18028 In ImageMagick 7.0.7-1 Q16, a memory exhaustion vulnerability was found in the function ReadTIFFImage in coders/tiff.c, which allow remote attackers to cause a… imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-12 medium6.5 CVE-2017-18027 In ImageMagick 7.0.7-1 Q16, a memory leak vulnerability was found in the function ReadMATImage in coders/mat.c, which allow remote attackers to cause a denial … imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-12 medium6.5 CVE-2018-5358 ImageMagick 7.0.7-22 Q16 has memory leaks in the EncodeImageAttributes function in coders/json.c, as demonstrated by the ReadPSDLayersInternal function in code… imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-12 medium6.5 CVE-2018-5357 ImageMagick 7.0.7-22 Q16 has memory leaks in the ReadDCMImage function in coders/dcm.c. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-12 high8.8 CVE-2018-5248 In ImageMagick 7.0.7-17 Q16, there is a heap-based buffer over-read in coders/sixel.c in the ReadSIXELImage function, related to the sixel_decode function. imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux 2018-01-05 medium6.5 CVE-2018-5247 In ImageMagick 7.0.7-17 Q16, there are memory leaks in ReadRLAImage in coders/rla.c. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-05 medium6.5 CVE-2018-5246 In ImageMagick 7.0.7-17 Q16, there are memory leaks in ReadPATTERNImage in coders/pattern.c. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-05 medium6.5 CVE-2017-18022 In ImageMagick 7.0.7-12 Q16, there are memory leaks in MontageImageCommand in MagickWand/montage.c. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-05 medium6.5 CVE-2017-1000476 ImageMagick 7.0.7-12 Q16, a CPU exhaustion vulnerability was found in the function ReadDDSInfo in coders/dds.c, which allows attackers to cause a denial of ser… imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux 2018-01-03 medium6.5 CVE-2017-1000445 ImageMagick 7.0.7-1 and older version are vulnerable to null pointer dereference in the MagickCore component and might lead to denial of service imagemagick · imagemagick, debian · debian_linux, canonical · ubuntu_linux 2018-01-02 medium6.5 CVE-2017-18008 In ImageMagick 7.0.7-17 Q16, there is a Memory Leak in ReadPWPImage in coders/pwp.c. imagemagick · imagemagick, canonical · ubuntu_linux 2018-01-01 medium6.5 CVE-2017-17934 ImageMagick 7.0.7-17 Q16 x86_64 has memory leaks in coders/msl.c, related to MSLPopImage and ProcessMSLScript, and associated with mishandling of MSLPushImage … imagemagick · imagemagick, canonical · ubuntu_linux 2017-12-27 medium6.5 CVE-2017-17914 In ImageMagick 7.0.7-16 Q16, a vulnerability was found in the function ReadOnePNGImage in coders/png.c, which allows attackers to cause a denial of service (Re… imagemagick · imagemagick, canonical · ubuntu_linux, debian · debian_linux 2017-12-27 medium6.5 CVE-2017-17887 In ImageMagick 7.0.7-16 Q16, a memory leak vulnerability was found in the function GetImagePixelCache in magick/cache.c, which allows attackers to cause a deni… imagemagick · imagemagick, canonical · ubuntu_linux 2017-12-27 medium6.5 CVE-2017-17886 In ImageMagick 7.0.7-12 Q16, a memory leak vulnerability was found in the function ReadPSDChannelZip in coders/psd.c, which allows attackers to cause a denial … imagemagick · imagemagick, canonical · ubuntu_linux 2017-12-27 medium6.5 CVE-2017-17885 In ImageMagick 7.0.7-12 Q16, a memory leak vulnerability was found in the function ReadPICTImage in coders/pict.c, which allows attackers to cause a denial of … imagemagick · imagemagick, canonical · ubuntu_linux 2017-12-27 medium6.5 CVE-2017-17884 In ImageMagick 7.0.7-16 Q16, a memory leak vulnerability was found in the function WriteOnePNGImage in coders/png.c, which allows attackers to cause a denial o… imagemagick · imagemagick, canonical · ubuntu_linux 2017-12-27

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.