NetSight

Security Dashboard

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

Reset
85 matching advisories · page 1 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2024-7867 In Xpdf 4.05 (and earlier), very large coordinates in a page box can cause an integer overflow and divide-by-zero. xpdfreader · xpdf 2024-08-15 medium5.5 CVE-2024-7866 In Xpdf 4.05 (and earlier), a PDF object loop in a pattern resource leads to infinite recursion and a stack overflow. xpdfreader · xpdf 2024-08-15 medium5.5 CVE-2024-4976 Out-of-bounds array write in Xpdf 4.05 and earlier, due to missing object type check in AcroForm field reference. xpdfreader · xpdf 2024-05-15 medium5.5 CVE-2022-48545 An infinite recursion in Catalog::findDestInTree can cause denial of service for xpdf 4.02. xpdfreader · xpdf 2023-08-22 medium5.5 CVE-2023-26930 Buffer Overflow vulnerability found in XPDF v.4.04 allows an attacker to cause a Denial of Service via the PDFDoc malloc in the pdftotext.cc function. xpdfreader · xpdf 2023-04-26 medium5.5 CVE-2022-45587 Stack overflow vulnerability in function gmalloc in goo/gmem.cc in xpdf 4.04, allows local attackers to cause a denial of service. xpdfreader · xpdf 2023-02-15 medium5.5 CVE-2022-45586 Stack overflow vulnerability in function Dict::find in xpdf/Dict.cc in xpdf 4.04, allows local attackers to cause a denial of service. xpdfreader · xpdf 2023-02-15 medium5.5 CVE-2022-43071 A stack overflow in the Catalog::readPageLabelTree2(Object*) function of XPDF v4.04 allows attackers to cause a Denial of Service (DoS) via a crafted PDF file. xpdfreader · xpdf 2022-11-15 medium5.5 CVE-2022-43295 XPDF v4.04 was discovered to contain a stack overflow via the function FileStream::copy() at xpdf/Stream.cc:795. xpdfreader · xpdf 2022-11-14 medium5.5 CVE-2022-41844 An issue was discovered in Xpdf 4.04. xpdfreader · xpdf 2022-09-30 medium5.5 CVE-2022-41843 An issue was discovered in Xpdf 4.04. xpdfreader · xpdf 2022-09-30 medium5.5 CVE-2022-41842 An issue was discovered in Xpdf 4.04. xpdfreader · xpdf 2022-09-30 medium5.5 CVE-2022-38334 XPDF v4.04 and earlier was discovered to contain a stack overflow via the function Catalog::countPageTree() at Catalog.cc. xpdfreader · xpdf 2022-09-15 medium5.5 CVE-2022-36561 XPDF v4.0.4 was discovered to contain a segmentation violation via the component /xpdf/AcroForm.cc:538. xpdfreader · xpdf 2022-08-30 medium5.5 CVE-2021-27548 There is a Null Pointer Dereference vulnerability in the XFAScanner::scanNode() function in XFAScanner.cc in xpdf 4.03. xpdfreader · xpdf 2022-05-18 medium5.5 CVE-2022-30775 xpdf 4.04 allocates excessive memory when presented with crafted input. xpdfreader · xpdf 2022-05-16 medium5.5 CVE-2022-27135 xpdf 4.03 has heap buffer overflow in the function readXRefTable located in XRef.cc. xpdfreader · xpdf 2022-04-25 medium5.0 CVE-2020-25725 In Xpdf 4.02, SplashOutputDev::endType3Char(GfxState *state) SplashOutputDev.cc:3079 is trying to use the freed `t3GlyphStack->cache`, which causes an `heap-us… xpdfreader · xpdf, fedoraproject · fedora 2020-11-21 medium5.5 CVE-2010-0207 In xpdf, the xref table contains an infinite loop which allows remote attackers to cause a denial of service (application crash) in xpdf-based PDF viewers. xpdfreader · xpdf 2019-10-30 medium5.5 CVE-2010-0206 xpdf allows remote attackers to cause a denial of service (NULL pointer dereference and crash) in the way it processes JBIG2 PDF stream objects. xpdfreader · xpdf 2019-10-30 medium5.5 CVE-2019-17064 Catalog.cc in Xpdf 4.02 has a NULL pointer dereference because Catalog.pageLabels is initialized too late in the Catalog constructor. glyphandcog · xpdfreader 2019-10-01 medium5.5 CVE-2019-16088 Xpdf 3.04 has a SIGSEGV in XRef::fetch in XRef.cc after many recursive calls to Catalog::countPageTree in Catalog.cc. glyphandcog · xpdfreader 2019-09-06 medium5.5 CVE-2019-15860 Xpdf 2.00 allows a SIGSEGV in XRef::constructXRef in XRef.cc. glyphandcog · xpdfreader 2019-09-03 medium5.5 CVE-2019-14294 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-14293 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-14292 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-14291 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-14290 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-14289 An issue was discovered in Xpdf 4.01.01. glyphandcog · xpdfreader 2019-07-27 medium5.5 CVE-2019-13291 In Xpdf 4.01.01, there is a heap-based buffer over-read in the function DCTStream::readScan() located at Stream.cc. glyphandcog · xpdfreader 2019-07-04

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.