NetSight

Security Dashboard

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

Reset
118 matching advisories · page 4 of 4Index updated 8 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.2 CVE-2010-5151 Race condition in avast! avast\! · avast\!_internet_security 2012-08-25 medium4.3 CVE-2012-1459 The TAR file parser in AhnLab V3 Internet Security 2011.01.18.00, Avira AntiVir 7.11.1.163, Antiy Labs AVL SDK 2.0.3.7, avast! ahnlab · v3_internet_security, alwil · avast_antivirus, anti-virus · vba32 +9 2012-03-21 medium4.3 CVE-2012-1457 The TAR file parser in Avira AntiVir 7.11.1.163, Antiy Labs AVL SDK 2.0.3.7, avast! aladdin · esafe, alwil · avast_antivirus, anti-virus · vba32 +9 2012-03-21 medium4.3 CVE-2012-1443 The RAR file parser in ClamAV 0.96.4, Rising Antivirus 22.83.00.03, Quick Heal (aka Cat QuickHeal) 11.00, G Data AntiVirus 21, AVEngine 20101.3.0.103 in Symant… ahnlab · v3_internet_security, aladdin · esafe, alwil · avast_antivirus +9 2012-03-21 critical9.3 CVE-2010-3126 Untrusted search path vulnerability in avast! avast · avast_antivirus_free 2010-08-26 high7.2 CVE-2010-0705 Aavmker4.sys in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2010-02-25 high7.2 CVE-2009-4049 Heap-based buffer overflow in aswRdr.sys (aka the TDI RDR driver) in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2009-11-23 high7.2 CVE-2009-3524 Unspecified vulnerability in ashWsFtr.dll in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2009-10-01 medium6.9 CVE-2009-3523 aavmKer4.sys in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2009-10-01 high7.2 CVE-2009-3522 Stack-based buffer overflow in aswMon2.sys in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2009-10-01 medium6.8 CVE-2008-6846 Multiple stack-based buffer overflows in avast! avast · avast_antivirus 2009-07-02 critical9.3 CVE-2008-5523 avast! avast · avast_antivirus 2008-12-12 medium6.8 CVE-2008-1625 aavmker4.sys in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2008-04-02 medium6.8 CVE-2007-6265 Unspecified vulnerability in avast! avast · avast_antivirus_home, avast · avast_antivirus_professional 2007-12-07 critical9.3 CVE-2007-2845 Heap-based buffer overflow in the CAB unpacker in avast! avast · avast_antivirus 2007-05-24 critical9.3 CVE-2007-2846 Heap-based buffer overflow in the SIS unpacker in avast! avas\!t · avast\!_antivirus, avast\! · avast\!_antivirus 2007-05-24 high7.8 CVE-2007-1673 unzoo.c, as used in multiple products including AMaViS 2.4.1 and earlier, allows remote attackers to cause a denial of service (infinite loop) via a ZOO archiv… amavis · amavis, avast · avast_antivirus, avast · avast_antivirus_home +9 2007-05-09 high7.8 CVE-2007-1672 avast! avast · avast_antivirus 2007-05-09 medium4.4 CVE-2007-0829 avast! alwil · avast_antivirus 2007-02-07 high7.5 CVE-2006-4626 Heap-based buffer overflow in alwil avast! alwil · avast_antivirus 2006-09-07 critical10.0 CVE-2006-2869 Unspecified vulnerability in the CHM unpacker in avast! alwil · avast_antivirus 2006-06-06 medium4.9 CVE-2006-1892 avast! alwil · avast_antivirus 2006-04-20 high7.2 CVE-2006-1355 avast! alwil · avast_antivirus 2006-03-22 medium5.1 CVE-2005-3214 Multiple interpretation error in unspecified versions of Avast Antivirus allows remote attackers to bypass virus detection via a malicious executable in a spec… alwil · avast_antivirus 2005-10-14 medium5.0 CVE-2005-2384 Directory traversal vulnerability in a third-party compression library (UNACEV2.DLL), as used in avast! alwil · avast_antivirus 2005-07-27 high7.5 CVE-2005-2385 Buffer overflow in a third-party compression library (UNACEV2.DLL), as used in avast! alwil · avast_antivirus 2005-07-27 high7.2 CVE-2005-1770 Buffer overflow in the Aavmker4 device driver in Avast! alwil · avast_antivirus 2005-05-31 high7.5 CVE-2005-1719 Unknown vulnerability in ALWIL avast! alwil · avast_antivirus 2005-05-24

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.