NetSight

Security Dashboard

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

Reset
136 matching advisories · page 4 of 5Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2015-6838 The xsl_ext_function_php function in ext/xsl/xsltprocessor.c in PHP before 5.4.45, 5.5.x before 5.5.29, and 5.6.x before 5.6.13, when libxml2 before 2.9.2 is u… php · php, xmlsoft · libxml2 2016-05-16 high7.5 CVE-2015-6837 The xsl_ext_function_php function in ext/xsl/xsltprocessor.c in PHP before 5.4.45, 5.5.x before 5.5.29, and 5.6.x before 5.6.13, when libxml2 before 2.9.2 is u… php · php, xmlsoft · libxml2 2016-05-16 high7.5 CVE-2015-8806 Denial of service or RCE from libxml2 and libxslt rubygems · nokogiri 2016-04-13 critical9.8 CVE-2015-8710 The htmlParseComment function in HTMLparser.c in libxml2 allows attackers to obtain sensitive information, cause a denial of service (out-of-bounds heap memory… xmlsoft · libxml2, debian · debian_linux 2016-04-11 high8.1 CVE-2016-1762 The xmlNextChar function in libxml2 before 2.9.4 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted XML document. apple · safari, apple · iphone_os, apple · mac_os_x +9 2016-03-24 medium6.5 CVE-2016-2073 The htmlParseNameComplex function in HTMLparser.c in libxml2 allows attackers to cause a denial of service (out-of-bounds read) via a crafted XML document. xmlsoft · libxml2, debian · debian_linux, canonical · ubuntu_linux 2016-02-12 medium5.0 CVE-2015-8317 The xmlParseXMLDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to obtain sensitive information via an (1) unterminated enc… debian · debian_linux, canonical · ubuntu_linux, xmlsoft · libxml2 +6 2015-12-15 medium5.8 CVE-2015-8242 The xmlSAX2TextNode function in SAX2.c in the push interface in the HTML parser in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of… xmlsoft · libxml2, hp · icewall_federation_agent, hp · icewall_file_manager +9 2015-12-15 medium6.4 CVE-2015-8241 The xmlNextChar function in libxml2 2.9.2 does not properly check the state, which allows context-dependent attackers to cause a denial of service (heap-based … debian · debian_linux, redhat · enterprise_linux_desktop, redhat · enterprise_linux_hpc_node +6 2015-12-15 medium5.0 CVE-2015-7500 The xmlParseMisc function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service (out-of-bounds heap read) via uns… hp · icewall_federation_agent, hp · icewall_file_manager, xmlsoft · libxml2 +9 2015-12-15 medium5.0 CVE-2015-7499 Heap-based buffer overflow in nokogiri rubygems · nokogiri 2015-12-15 medium5.0 CVE-2015-7498 Heap-based buffer overflow in the xmlParseXmlDecl function in parser.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of service … hp · icewall_federation_agent, hp · icewall_file_manager, canonical · ubuntu_linux +6 2015-12-15 medium5.0 CVE-2015-7497 Heap-based buffer overflow in the xmlDictComputeFastQKey function in dict.c in libxml2 before 2.9.3 allows context-dependent attackers to cause a denial of ser… debian · debian_linux, canonical · ubuntu_linux, xmlsoft · libxml2 +6 2015-12-15 high7.1 CVE-2015-5312 Nokogiri subject to DoS via libxml2 vulnerability rubygems · nokogiri 2015-12-15 low2.6 CVE-2015-8035 The xz_decomp function in xzlib.c in libxml2 2.9.1 does not properly detect compression errors, which allows context-dependent attackers to cause a denial of s… debian · debian_linux, xmlsoft · libxml2, apple · iphone_os +4 2015-11-18 medium6.8 CVE-2015-7942 The xmlParseConditionalSections function in parser.c in libxml2 does not properly skip intermediary entities when it stops parsing invalid input, which allows … hp · icewall_federation_agent, hp · icewall_file_manager, debian · debian_linux +6 2015-11-18 medium4.3 CVE-2015-7941 libxml2 2.9.2 does not properly stop parsing invalid input, which allows context-dependent attackers to cause a denial of service (out-of-bounds read and libxm… canonical · ubuntu_linux, xmlsoft · libxml2 2015-11-18 medium5.0 CVE-2015-7995 The xsltStylePreCompute function in preproc.c in libxslt 1.1.28 does not check if the parent node is an element, which allows attackers to cause a denial of se… apple · iphone_os, apple · mac_os_x, apple · tvos +2 2015-11-17 medium5.0 CVE-2015-1819 Nokogiri vulnerable to libxml XML Entity Expansion rubygems · nokogiri 2015-08-14 medium5.0 CVE-2014-3660 parser.c in libxml2 before 2.9.2 does not properly prevent entity expansion even when entity substitution has been disabled, which allows context-dependent att… xmlsoft · libxml2, apple · mac_os_x, canonical · ubuntu_linux +2 2014-11-04 medium6.8 CVE-2013-0339 libxml2 through 2.9.1 does not properly handle external entities expansion unless an application developer uses the xmlSAX2ResolveEntity or xmlSetExternalEntit… xmlsoft · libxml2, canonical · ubuntu_linux, debian · debian_linux +1 2014-01-21 medium4.3 CVE-2013-4520 xslt.c in libxslt before 1.1.25 allows context-dependent attackers to cause a denial of service (crash) via a stylesheet that embeds a DTD, which causes a stru… xmlsoft · libxslt 2013-12-14 medium5.0 CVE-2013-2877 parser.c in libxml2 before 2.9.0, as used in Google Chrome before 28.0.1500.71 and other products, allows remote attackers to cause a denial of service (out-of… google · chrome, xmlsoft · libxml2 2013-07-10 high7.5 CVE-2013-1969 Multiple use-after-free vulnerabilities in libxml2 2.9.0 and possibly other versions might allow context-dependent attackers to cause a denial of service (cras… xmlsoft · libxml2 2013-04-25 medium4.3 CVE-2013-0338 libxml2 2.9.0 and earlier allows context-dependent attackers to cause a denial of service (CPU and memory consumption) via an XML file containing an entity dec… xmlsoft · libxml2, canonical · ubuntu_linux, opensuse · opensuse 2013-04-25 medium5.0 CVE-2012-6139 libxslt before 1.1.28 allows remote attackers to cause a denial of service (NULL pointer dereference and crash) via an (1) empty match attribute in a XSL key t… xmlsoft · libxslt, opensuse · opensuse 2013-04-12 medium5.0 CVE-2012-0841 libxml2 before 2.8.0 computes hash values without restricting the ability to trigger hash collisions predictably, which allows context-dependent attackers to c… xmlsoft · libxml2, apple · iphone_os 2012-12-21 medium6.8 CVE-2012-5134 Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and … google · chrome, xmlsoft · libxml2, apple · iphone_os 2012-11-28 medium6.8 CVE-2012-2871 libxml2 2.9.0-rc1 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly support a cast of an unspecified variable during handling of XSL… apple · iphone_os, google · chrome, xmlsoft · libxml2 2012-08-31 medium4.3 CVE-2012-2870 libxslt 1.1.26 and earlier, as used in Google Chrome before 21.0.1180.89, does not properly manage memory, which might allow remote attackers to cause a denial… apple · iphone_os, google · chrome, xmlsoft · libxslt 2012-08-31

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.