NetSight

Security Dashboard

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

Reset
85 matching advisories · page 2 of 3Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2019-13288 In Xpdf 4.01.01, the Parser::getObj() function in Parser.cc may cause infinite recursion via a crafted file. glyphandcog · xpdfreader 2019-07-04 medium5.5 CVE-2019-13287 In Xpdf 4.01.01, there is an out-of-bounds read vulnerability in the function SplashXPath::strokeAdjust() located at splash/SplashXPath.cc. glyphandcog · xpdfreader 2019-07-04 medium5.5 CVE-2019-13286 In Xpdf 4.01.01, there is a heap-based buffer over-read in the function JBIG2Stream::readTextRegionSeg() located at JBIG2Stream.cc. glyphandcog · xpdfreader, fedoraproject · fedora 2019-07-04 medium5.5 CVE-2019-12958 In Xpdf 4.01.01, a heap-based buffer over-read could be triggered in FoFiType1C::convertToType0 in fofi/FoFiType1C.cc when it is trying to access the second pr… glyphandcog · xpdfreader 2019-06-25 medium5.5 CVE-2019-10026 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10025 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10024 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10023 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10022 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10021 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10020 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10019 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf 2019-03-25 medium5.5 CVE-2019-10018 An issue was discovered in Xpdf 4.01.01. xpdfreader · xpdf, debian · debian_linux, canonical · ubuntu_linux 2019-03-25 medium5.5 CVE-2018-18651 An issue was discovered in Xpdf 4.00. xpdfreader · xpdf 2018-10-25 medium5.5 CVE-2018-18650 An issue was discovered in Xpdf 4.00. xpdfreader · xpdf 2018-10-25 medium5.5 CVE-2018-18459 The function DCTStream::getBlock in Stream.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted pdf fi… xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-18458 The function DCTStream::decodeImage in Stream.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted pdf… xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-18457 The function DCTStream::readScan in Stream.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted pdf fi… xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-18456 The function Object::isName() in Object.h (called from Gfx::opSetFillColorN) in Xpdf 4.00 allows remote attackers to cause a denial of service (stack-based buf… xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-18455 The GfxImageColorMap class in GfxState.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted pdf fil… xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-18454 CCITTFaxStream::readRow() in Stream.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted pdf file, … xpdfreader · xpdf 2018-10-18 medium5.5 CVE-2018-16369 XRef::fetch in XRef.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (stack consumption) via a crafted pdf file, related to AcroForm::scanF… xpdfreader · xpdf 2018-09-03 medium5.5 CVE-2018-16368 SplashXPath::strokeAdjust in splash/SplashXPath.cc in Xpdf 4.00 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafte… xpdfreader · xpdf 2018-09-03 medium5.5 CVE-2018-8107 The JPXStream::close function in JPXStream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and application crash) via… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8106 The JPXStream::readTilePartData function in JPXStream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and application… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8105 The JPXStream::fillReadBuf function in JPXStream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and application cras… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8104 The BufStream::lookChar function in Stream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and application crash) via… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8103 The JBIG2Stream::readGenericBitmap function in JBIG2Stream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and applic… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8102 The JBIG2MMRDecoder::getBlackCode function in JBIG2Stream.cc in xpdf 4.00 allows attackers to launch denial of service (buffer over-read and application crash)… xpdfreader · xpdf 2018-03-14 medium5.5 CVE-2018-8101 The JPXStream::inverseTransformLevel function in JPXStream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer over-read and applic… xpdfreader · xpdf 2018-03-14

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.