NetSight

Security Dashboard

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

Reset
125 matching advisories · page 4 of 5Index updated 9 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2018-5772 In Exiv2 0.26, there is a segmentation fault caused by uncontrolled recursion in the Exiv2::Image::printIFDStructure function in the image.cpp file. exiv2 · exiv2 2018-01-18 medium5.5 CVE-2018-4868 The Exiv2::Jp2Image::readMetadata function in jp2image.cpp in Exiv2 0.26 allows remote attackers to cause a denial of service (excessive memory allocation) via… exiv2 · exiv2 2018-01-03 medium5.5 CVE-2017-18005 Exiv2 0.26 has a Null Pointer Dereference in the Exiv2::DataValue::toLong function in value.cpp, related to crafted metadata in a TIFF file. exiv2 · exiv2, debian · debian_linux 2017-12-31 medium5.5 CVE-2017-17669 There is a heap-based buffer over-read in the Exiv2::Internal::PngChunk::keyTXTChunk function of pngchunk_int.cpp in Exiv2 0.26. exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-12-13 medium5.5 CVE-2017-1000128 Exiv2 0.26 contains a stack out of bounds read in JPEG2000 parser exiv2 · exiv2 2017-11-17 medium5.5 CVE-2017-1000127 Exiv2 0.26 contains a heap buffer overflow in tiff parser exiv2 · exiv2 2017-11-17 medium5.5 CVE-2017-1000126 exiv2 0.26 contains a Stack out of bounds read in webp parser exiv2 · exiv2 2017-11-17 medium5.5 CVE-2017-14866 There is a heap-based buffer overflow in the Exiv2::s2Data function of types.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14865 There is a heap-based buffer overflow in the Exiv2::us2Data function of types.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14864 An Invalid memory address dereference was discovered in Exiv2::getULong in types.cpp in Exiv2 0.26. exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-09-29 medium5.5 CVE-2017-14863 A NULL pointer dereference was discovered in Exiv2::Image::printIFDStructure in image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14862 An Invalid memory address dereference was discovered in Exiv2::DataValue::read in value.cpp in Exiv2 0.26. exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-09-29 medium5.5 CVE-2017-14861 There is a stack consumption vulnerability in the Exiv2::Internal::stringFormat function of image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14860 There is a heap-based buffer over-read in the Exiv2::Jp2Image::readMetadata function of jp2image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14859 An Invalid memory address dereference was discovered in Exiv2::StringValueBase::read in value.cpp in Exiv2 0.26. exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-09-29 medium5.5 CVE-2017-14858 There is a heap-based buffer overflow in the Exiv2::l2Data function of types.cpp in Exiv2 0.26. exiv2 · exiv2 2017-09-29 medium5.5 CVE-2017-14857 In Exiv2 0.26, there is an invalid free in the Image class in image.cpp that leads to a Segmentation fault. exiv2 · exiv2 2017-09-29 medium6.5 CVE-2017-12957 There is a heap-based buffer over-read in libexiv2 in Exiv2 0.26 that is triggered in the Exiv2::Image::io function in image.cpp. exiv2 · exiv2 2017-08-18 medium6.5 CVE-2017-12956 There is an illegal address access in Exiv2::FileIo::path[abi:cxx11]() in basicio.cpp of libexiv2 in Exiv2 0.26 that will lead to remote denial of service. exiv2 · exiv2 2017-08-18 high8.8 CVE-2017-12955 There is a heap-based buffer overflow in basicio.cpp of Exiv2 0.26. exiv2 · exiv2 2017-08-18 medium6.5 CVE-2017-11683 There is a reachable assertion in the Internal::TiffReader::visitDirectory function in tiffvisitor.cpp of Exiv2 0.26 that will lead to a remote denial of servi… exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-07-27 high7.5 CVE-2017-11592 There is a Mismatched Memory Management Routines vulnerability in the Exiv2::FileIo::seek function of Exiv2 0.26 that will lead to a remote denial of service a… exiv2 · exiv2 2017-07-24 high7.5 CVE-2017-11591 There is a Floating point exception in the Exiv2::ValueType function in Exiv2 0.26 that will lead to a remote denial of service attack via crafted input. exiv2 · exiv2, canonical · ubuntu_linux, debian · debian_linux 2017-07-24 high7.5 CVE-2017-11553 There is an illegal address access in the extend_alias_table function in localealias.c of Exiv2 0.26. exiv2 · exiv2 2017-07-23 medium6.5 CVE-2017-11340 There is a Segmentation fault in the XmpParser::terminate() function in Exiv2 0.26, related to an exit call. exiv2 · exiv2 2017-07-17 medium6.5 CVE-2017-11339 There is a heap-based buffer overflow in the Image::printIFDStructure function of image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-07-17 medium6.5 CVE-2017-11338 There is an infinite loop in the Exiv2::Image::printIFDStructure function of image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-07-17 medium6.5 CVE-2017-11337 There is an invalid free in the Action::TaskFactory::cleanup function of actions.cpp in Exiv2 0.26. exiv2 · exiv2 2017-07-17 medium6.5 CVE-2017-11336 There is a heap-based buffer over-read in the Image::printIFDStructure function in image.cpp in Exiv2 0.26. exiv2 · exiv2 2017-07-17 high7.5 CVE-2017-9953 There is an invalid free in Image::printIFDStructure that leads to a Segmentation fault in Exiv2 0.26. exiv2 · exiv2, redhat · enterprise_linux 2017-06-26

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.