NetSight

Security Dashboard

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

Reset
126 matching advisories · page 3 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high8.8 CVE-2018-20429 libming 0.4.8 has a NULL pointer dereference in the getName function of the decompile.c file, a different vulnerability than CVE-2018-7872 and CVE-2018-9165. libming · libming 2018-12-24 high8.8 CVE-2018-20428 libming 0.4.8 has a NULL pointer dereference in the strlenext function of the decompile.c file, a different vulnerability than CVE-2018-7874. libming · libming 2018-12-24 high8.8 CVE-2018-20427 libming 0.4.8 has a NULL pointer dereference in the getInt function of the decompile.c file, a different vulnerability than CVE-2018-9132. libming · libming 2018-12-24 high8.8 CVE-2018-20426 libming 0.4.8 has a NULL pointer dereference in the newVar3 function of the decompile.c file, a different vulnerability than CVE-2018-7866. libming · libming 2018-12-24 high8.8 CVE-2018-20425 libming 0.4.8 has a NULL pointer dereference in the pushdup function of the decompile.c file. libming · libming 2018-12-24 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 high7.5 CVE-2018-13066 There is a memory leak in util/parser.c in libming 0.4.8, which will lead to a denial of service via parseSWF_DEFINEBUTTON2, parseSWF_DEFINEFONT, parseSWF_DEFI… libming · libming 2018-07-02 high8.8 CVE-2018-11226 The getString function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, which allo… libming · libming 2018-05-17 high8.8 CVE-2018-11225 The dcputs function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, which allows … libming · libming 2018-05-17 high8.8 CVE-2018-11100 The decompileSETTARGET function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, w… libming · libming 2018-05-15 high8.8 CVE-2018-11095 The decompileJUMP function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, which … libming · libming 2018-05-15 high8.8 CVE-2018-11017 The newVar_N function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, which allow… libming · libming 2018-05-13 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 high8.8 CVE-2018-9009 In libming 0.4.8, there is a use-after-free in the decompileJUMP function of the decompile.c file. libming · libming, debian · debian_linux 2018-03-25 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

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.