NetSight

Security Dashboard

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

Reset
280 matching advisories · page 7 of 10Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2019-11938 Java Facebook Thrift servers would not error upon receiving messages declaring containers of sizes larger than the payload. facebook · thrift 2020-03-10 high7.5 CVE-2020-1893 Insufficient boundary checks when decoding JSON in TryParse reads out of bounds memory, potentially leading to DOS. facebook · hhvm 2020-03-03 high8.1 CVE-2020-1892 Insufficient boundary checks when decoding JSON in JSON_parser allows read access to out of bounds memory, potentially leading to information leak and DOS. facebook · hhvm 2020-03-03 high7.5 CVE-2020-1888 Insufficient boundary checks when decoding JSON in handleBackslash reads out of bounds memory, potentially leading to DOS. facebook · hhvm 2020-03-03 medium5.3 CVE-2016-1000109 HHVM does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of untrusted cli… facebook · hhvm 2020-02-19 critical9.8 CVE-2016-1000005 mcrypt_get_block_size did not enforce that the provided "module" parameter was a string, leading to type confusion if other types of data were passed in. facebook · hhvm 2020-02-19 critical9.8 CVE-2016-1000004 Insufficient type checks were employed prior to casting input data in SimpleXMLElement_exportNode and simplexml_import_dom. facebook · hhvm 2020-02-19 critical9.8 CVE-2011-3614 An Access Control vulnerability exists in the Facebook, Twitter, and Embedded plugins in Vanilla Forums before 2.0.17.9. vanillaforums · vanilla 2020-01-22 high7.5 CVE-2013-4593 omniauth-facebook Improper Authentication vulnerability rubygems · omniauth-facebook 2019-12-11 high8.8 CVE-2019-19684 nopCommerce v4.2.0 allows privilege escalation via file upload in Presentation/Nop.Web/Admin/Areas/Controllers/PluginController.cs via Admin/FacebookAuthentica… nopcommerce · nopcommerce 2019-12-09 critical9.8 CVE-2019-11940 In the course of decompressing HPACK inside the HTTP2 protocol, an unexpected sequence of header table resize operations can place the header table into a corr… facebook · proxygen 2019-12-04 critical9.8 CVE-2019-11936 Various APC functions accept keys containing null bytes as input, leading to premature truncation of input. facebook · hhvm 2019-12-04 critical9.8 CVE-2019-11935 Insufficient boundary checks when processing a string in mb_ereg_replace allows access to out-of-bounds memory. facebook · hhvm 2019-12-04 critical9.8 CVE-2019-11934 Improper handling of close_notify alerts can result in an out-of-bounds read in AsyncSSLSocket. facebook · folly 2019-12-04 critical9.8 CVE-2019-11930 An invalid free in mb_detect_order can cause the application to crash or potentially result in remote code execution. facebook · hhvm 2019-12-04 high7.5 CVE-2019-11937 In Mcrouter prior to v0.41.0, a large struct input provided to the Carbon protocol reader could result in stack exhaustion and denial of service. facebook · mcrouter 2019-12-04 high7.5 CVE-2019-11923 In Mcrouter prior to v0.41.0, the deprecated ASCII parser would allocate a buffer to a user-specified length with no maximum length enforced, allowing for reso… facebook · mcrouter 2019-12-04 critical9.8 CVE-2016-1000006 hhvm before 3.12.11 has a use-after-free in the serialize_memoize_param() and ResourceBundle::__construct() functions. facebook · hhvm 2019-11-19 critical9.8 CVE-2019-11929 Insufficient boundary checks when formatting numbers in number_format allows read/write access to out-of-bounds memory, potentially leading to remote code exec… facebook · hhvm 2019-10-02 medium6.5 CVE-2015-9433 The wp-social-bookmarking-light plugin before 1.7.10 for WordPress has CSRF with resultant XSS via configuration parameters for Tumblr, Twitter, Facebook, etc. wp_social_bookmarking_light_project · wp_social_bookmarking_light 2019-09-26 high8.8 CVE-2016-10989 The leenkme plugin before 2.6.0 for WordPress has wp-admin/admin.php?page=leenkme_facebook CSRF. leenk · leenk.me 2019-09-17 medium6.1 CVE-2016-10988 The leenkme plugin before 2.6.0 for WordPress has stored XSS via facebook_message, facebook_linkname, facebook_caption, facebook_description, default_image, or… leenk · leenk.me 2019-09-17 critical9.8 CVE-2019-11926 Insufficient boundary checks when processing M_SOFx markers from JPEG headers in the GD extension could allow access to out-of-bounds memory via a maliciously … facebook · hhvm 2019-09-06 critical9.8 CVE-2019-11925 Insufficient boundary checks when processing the JPEG APP12 block marker in the GD extension could allow access to out-of-bounds memory via a maliciously const… facebook · hhvm 2019-09-06 high8.8 CVE-2019-15841 The facebook-for-woocommerce plugin before 1.9.15 for WordPress has CSRF via ajax_woo_infobanner_post_click, ajax_woo_infobanner_post_xout, or ajax_fb_toggle_v… facebook · facebook_for_woocommerce 2019-08-30 high8.8 CVE-2019-15840 The facebook-for-woocommerce plugin before 1.9.14 for WordPress has CSRF. facebook · facebook_for_woocommerce 2019-08-30 high8.8 CVE-2019-15781 The facebook-by-weblizar plugin before 2.8.5 for WordPress has CSRF. weblizar · social_likebox_\&_feed 2019-08-29 critical9.8 CVE-2015-9351 The feed-them-social plugin before 1.7.0 for WordPress has possible shortcode execution in the Facebook Feeds load more button. slickremix · feed_them_social 2019-08-27 medium6.1 CVE-2015-9350 The feed-them-social plugin before 1.7.0 for WordPress has reflected XSS in the Facebook Feeds load more button. slickremix · feed_them_social 2019-08-27 high7.5 CVE-2019-11924 A peer could send empty handshake fragments containing only padding which would be kept in memory until a full handshake was received, resulting in memory exha… facebook · fizz 2019-08-20

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.