NetSight

Security Dashboard

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

Reset
77 matching advisories · page 1 of 3Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.3 CVE-2024-26337 swftools v0.9.2 was discovered to contain a segmentation violation via the function s_font at swftools/src/swfc.c. swftools · swftools 2024-03-05 medium5.5 CVE-2024-26335 swftools v0.9.2 was discovered to contain a segmentation violation via the function state_free at swftools/src/swfc-history.c. swftools · swftools 2024-03-05 medium6.2 CVE-2024-26334 swftools v0.9.2 was discovered to contain a segmentation violation via the function compileSWFActionCode at swftools/lib/action/actioncompiler.c. swftools · swftools 2024-03-05 medium5.5 CVE-2024-26333 swftools v0.9.2 was discovered to contain a segmentation violation via the function free_lines at swftools/lib/modules/swfshape.c. swftools · swftools 2024-03-05 medium5.5 CVE-2024-22957 swftools 0.9.2 was discovered to contain an Out-of-bounds Read vulnerability via the function dict_do_lookup in swftools/lib/q.c:1190. swftools · swftools 2024-01-19 medium5.5 CVE-2024-22914 A heap-use-after-free was found in SWFTools v0.9.2, in the function input at lex.swf5.c:2620. swftools · swftools 2024-01-19 medium5.5 CVE-2023-37644 SWFTools 0.9.2 772e55a allows attackers to trigger a large memory-allocation attempt via a crafted document, as demonstrated by pdf2swf. swftools · swftools 2024-01-11 medium5.5 CVE-2023-29950 swfrender v0.9.2 was discovered to contain a heap buffer overflow in the function enumerateUsedIDs_fillstyle at modules/swftools.c swftools · swftools 2023-04-27 medium5.5 CVE-2023-27249 swfdump v0.9.2 was discovered to contain a heap buffer overflow in the function swf_GetPlaceObject at swfobject.c. swftools · swftools 2023-03-23 medium5.5 CVE-2022-46440 ttftool v0.9.2 was discovered to contain a segmentation violation via the readU16 function at ttf.c. swftools · swftools 2023-02-24 medium5.5 CVE-2022-35081 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via png_read_header at /src/png2swf.c. swftools · swftools 2022-10-13 medium5.5 CVE-2022-35080 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via png_load at /lib/png.c. swftools · swftools 2022-10-13 medium5.5 CVE-2022-35099 SWFTools commit 772e55a2 was discovered to contain a stack overflow via ImageStream::getPixel(unsigned char*) at /xpdf/Stream.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35098 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via GfxICCBasedColorSpace::getDefaultColor(GfxColor*) at /xpdf/GfxState.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35097 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via FoFiTrueType::writeTTF at /xpdf/FoFiTrueType.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35096 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via draw_stroke at /gfxpoly/stroke.c. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35095 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via InfoOutputDev::type3D1 at /pdf/InfoOutputDev.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35094 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via DCTStream::readHuffSym(DCTHuffTable*) at /xpdf/Stream.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35093 SWFTools commit 772e55a2 was discovered to contain a global buffer overflow via DCTStream::transformDataUnit at /xpdf/Stream.cc. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35092 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via convert_gfxline at /gfxpoly/convert.c. swftools · swftools 2022-09-23 medium5.5 CVE-2022-35091 SWFTools commit 772e55a2 was discovered to contain a floating point exception (FPE) via DCTStream::readMCURow() at /xpdf/Stream.cc.ow() swftools · swftools 2022-09-23 medium5.5 CVE-2022-35090 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via __asan_memcpy at /asan/asan_interceptors_memintrinsics.cpp:. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35089 SWFTools commit 772e55a2 was discovered to contain a heap-buffer-overflow via getTransparentColor at /home/bupt/Desktop/swftools/src/gif2swf. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35088 SWFTools commit 772e55a2 was discovered to contain a heap buffer-overflow via getGifDelayTime at /home/bupt/Desktop/swftools/src/src/gif2swf.c. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35087 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via MovieAddFrame at /src/gif2swf.c. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35086 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via /multiarch/memmove-vec-unaligned-erms.S. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35085 SWFTools commit 772e55a2 was discovered to contain a memory leak via /lib/mem.c. swftools · swftools 2022-09-21 medium5.5 CVE-2022-35114 SWFTools commit 772e55a2 was discovered to contain a segmentation violation via extractFrame at /readers/swf.c. swftools · swftools 2022-08-16 medium5.5 CVE-2022-35113 SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via swf_DefineLosslessBitsTagToImage at /modules/swfbits.c. swftools · swftools 2022-08-16 medium5.5 CVE-2022-35111 SWFTools commit 772e55a2 was discovered to contain a stack overflow via __sanitizer::StackDepotNode::hash(__sanitizer::StackTrace const&) at /sanitizer_common/… swftools · swftools 2022-08-16

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.