NetSight

Security Dashboard

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

Reset
84 matching advisories · page 2 of 3Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2021-34340 Ming 0.4.8 has an out-of-bounds buffer access issue in the function decompileINCR_DECR() in decompiler.c file that causes a direct segmentation fault and leads… libming · ming, fedoraproject · fedora 2022-03-10 medium6.5 CVE-2021-34339 Ming 0.4.8 has an out-of-bounds buffer access issue in the function getString() in decompiler.c file that causes a direct segmentation fault and leads to denia… libming · ming, fedoraproject · fedora 2022-03-10 medium6.5 CVE-2021-34338 Ming 0.4.8 has an out-of-bounds buffer overwrite issue in the function getName() in decompiler.c file that causes a direct segmentation fault and leads to deni… libming · ming, fedoraproject · fedora 2022-03-10 medium6.5 CVE-2021-44591 In libming 0.4.8, the parseSWF_DEFINELOSSLESS2 function in util/parser.c lacks a boundary check that would lead to denial-of-service attacks via a crafted SWF … libming · libming 2022-01-06 medium6.5 CVE-2021-44590 In libming 0.4.8, a memory exhaustion vulnerability exist in the function cws2fws in util/main.c. libming · libming 2022-01-06 medium6.5 CVE-2020-6629 Ming (aka libming) 0.4.8 has z NULL pointer dereference in the function decompileGETURL2() in decompile.c. libming · libming 2020-01-09 medium6.5 CVE-2019-12982 Ming (aka libming) 0.4.8 has a heap buffer overflow and underflow in the decompileCAST function in util/decompile.c in libutil.a. libming · libming 2019-06-26 medium6.5 CVE-2019-12980 In Ming (aka libming) 0.4.8, there is an integer overflow (caused by an out-of-range left shift) in the SWFInput_readSBits function in blocks/input.c. libming · libming 2019-06-26 medium6.5 CVE-2019-3572 An issue was discovered in libming 0.4.8. libming · libming 2019-01-02 medium6.5 CVE-2018-20591 A heap-based buffer over-read was discovered in decompileJUMP function in util/decompile.c of libming v0.4.8. libming · libming 2018-12-30 medium6.5 CVE-2018-15871 An invalid memory address dereference was discovered in decompileSingleArgBuiltInFunctionCall in libming 0.4.8 before 2018-03-12. libming · libming 2018-08-25 medium6.5 CVE-2018-15870 An invalid memory address dereference was discovered in decompileGETVARIABLE in libming 0.4.8 before 2018-03-12. libming · libming 2018-08-25 medium6.5 CVE-2018-13251 In libming 0.4.8, there is an excessive memory allocation attempt in the readBytes function of the util/read.c file, related to parseSWF_DEFINEBITSJPEG2. libming · libming 2018-07-05 medium6.5 CVE-2018-13250 libming 0.4.8 has a NULL pointer dereference in the getString function of the decompile.c file, related to decompileSTRINGCONCAT. libming · libming 2018-07-05 medium6.5 CVE-2018-9165 The pushdup function in util/decompile.c in libming through 0.4.8 does not recognize the need for ActionPushDuplicate to perform a deep copy when a String is a… libming · libming 2018-04-01 medium6.5 CVE-2018-9132 libming 0.4.8 has a NULL pointer dereference in the getInt function of the decompile.c file. libming · libming, debian · debian_linux 2018-03-30 medium6.5 CVE-2018-8964 In libming 0.4.8, the decompileDELETE function of decompile.c has a use-after-free. libming · libming 2018-03-23 medium6.5 CVE-2018-8963 In libming 0.4.8, the decompileGETVARIABLE function of decompile.c has a use-after-free. libming · libming 2018-03-23 medium6.5 CVE-2018-8962 In libming 0.4.8, the decompileSingleArgBuiltInFunctionCall function of decompile.c has a use-after-free. libming · libming 2018-03-23 medium6.5 CVE-2018-8961 In libming 0.4.8, the decompilePUSHPARAM function of decompile.c has a use-after-free. libming · libming 2018-03-23 medium6.5 CVE-2018-8807 In libming 0.4.8, these is a use-after-free in the function decompileCALLFUNCTION of decompile.c. libming · libming 2018-03-20 medium6.5 CVE-2018-8806 In libming 0.4.8, there is a use-after-free in the decompileArithmeticOp function of decompile.c. libming · libming 2018-03-20 medium6.5 CVE-2018-7877 There is a heap-based buffer overflow in the getString function of util/decompile.c in libming 0.4.8 for DOUBLE data. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7876 In libming 0.4.8, a memory exhaustion vulnerability was found in the function parseSWF_ACTIONRECORD in util/parser.c, which allows remote attackers to cause a … libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7875 There is a heap-based buffer over-read in the getString function of util/decompile.c in libming 0.4.8 for CONSTANT8 data. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7874 An invalid memory address dereference was discovered in strlenext in util/decompile.c in libming 0.4.8. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7873 There is a heap-based buffer overflow in the getString function of util/decompile.c in libming 0.4.8 for INTEGER data. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7872 An invalid memory address dereference was discovered in the function getName in libming 0.4.8 for CONSTANT16 data. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7870 An invalid memory address dereference was discovered in getString in util/decompile.c in libming 0.4.8 for CONSTANT16 data. libming · libming, debian · debian_linux 2018-03-08 medium6.5 CVE-2018-7868 There is a heap-based buffer over-read in the getName function of util/decompile.c in libming 0.4.8 for CONSTANT8 data. libming · libming, debian · debian_linux 2018-03-08

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.