NetSight

Security Dashboard

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

Reset
280 matching advisories · page 6 of 10Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.8 CVE-2021-24330 The Funnel Builder by CartFlows – Create High Converting Sales Funnels For WordPress plugin before 1.6.13 did not sanitise its facebook_pixel_id and google_ana… cartflows · cartflows 2021-06-01 high7.5 CVE-2020-1920 Regular expression denial of service in react-native npm · react-native 2021-06-01 critical9.8 CVE-2021-24028 An invalid free in Thrift's table-based serialization can cause the application to crash or potentially result in code execution or other undesirable effects. facebook · thrift 2021-04-14 high8.8 CVE-2021-24218 The wp_ajax_save_fbe_settings and wp_ajax_delete_fbe_settings AJAX actions of the Facebook for WordPress plugin before 3.0.4 were vulnerable to CSRF due to a l… facebook · facebook 2021-04-12 high8.1 CVE-2021-24217 The run_action function of the Facebook for WordPress plugin before 3.0.0 deserializes user supplied data making it possible for PHP objects to be supplied cre… facebook · facebook 2021-04-12 high7.5 CVE-2021-24029 A packet of death scenario is possible in mvfst via a specially crafted message during a QUIC session, which causes a crash via a failed assertion. facebook · mvfst, facebook · proxygen 2021-03-15 critical9.8 CVE-2020-1900 When unserializing an object with dynamic properties HHVM needs to pre-reserve the full size of the dynamic property array before inserting anything into it. facebook · hhvm 2021-03-11 high7.5 CVE-2020-1899 The unserialize() function supported a type code, "S", which was meant to be supported only for APC serialization. facebook · hhvm 2021-03-11 high7.5 CVE-2020-1898 The fb_unserialize function did not impose a depth limit for nested deserialization. facebook · hhvm 2021-03-11 critical9.8 CVE-2021-24030 The fbgames protocol handler registered as part of Facebook Gameroom does not properly quote arguments passed to the executable. facebook · gameroom 2021-03-10 critical9.8 CVE-2021-24025 Due to incorrect string size calculations inside the preg_quote function, a large input string passed to the function can trigger an integer overflow leading t… facebook · hhvm 2021-03-10 high7.5 CVE-2020-1921 In the crypt function, we attempt to null terminate a buffer using the size of the input salt without validating that the offset is within the buffer. facebook · hhvm 2021-03-10 high7.5 CVE-2020-1919 Incorrect bounds calculations in substr_compare could lead to an out-of-bounds read when the second string argument passed in is longer than the first. facebook · hhvm 2021-03-10 high7.5 CVE-2020-1918 In-memory file operations (ie: using fopen on a data URI) did not properly restrict negative seeking, allowing for the reading of memory prior to the in-memory… facebook · hhvm 2021-03-10 critical9.8 CVE-2020-1917 xbuf_format_converter, used as part of exif_read_data, was appending a terminating null character to the generated string, but was not using its standard appen… facebook · hhvm 2021-03-10 critical9.8 CVE-2020-1916 An incorrect size calculation in ldap_escape may lead to an integer overflow when overly long input is passed in, resulting in an out-of-bounds write. facebook · hhvm 2021-03-10 medium5.6 CVE-2021-24033 react-dev-utils OS Command Injection in function `getProcessForPort` npm · react-dev-utils 2021-03-09 medium4.7 CVE-2021-24032 Beginning in v1.4.1 and prior to v1.4.9, due to an incomplete fix for CVE-2021-24031, the Zstandard command-line utility created output files with default perm… facebook · zstandard 2021-03-04 medium5.5 CVE-2021-24031 In the Zstandard command-line utility prior to v1.4.1, output files were created with default permissions. facebook · zstandard 2021-03-04 critical9.8 CVE-2020-1896 A stack overflow vulnerability in Facebook Hermes 'builtin apply' prior to commit 86543ac47e59c522976b5632b8bf9a2a4583c7d2 (https://github.com/facebook/hermes/… facebook · hermes 2021-02-02 high7.5 CVE-2020-1915 Out-of-bounds Read in Facebook Hermes npm · hermes-engine 2020-10-26 critical9.8 CVE-2020-1914 Always-Incorrect Control Flow Implementation in Facebook Hermes npm · hermes-engine 2020-10-08 high7.5 CVE-2020-26575 In Wireshark through 3.2.7, the Facebook Zero Protocol (aka FBZERO) dissector could enter an infinite loop. wireshark · wireshark, fedoraproject · fedora, debian · debian_linux +1 2020-10-06 high8.1 CVE-2020-1913 Signed to Unsigned Conversion Error in Facebook Hermes npm · hermes-engine 2020-09-09 high8.1 CVE-2020-1912 Out-of-bounds Read and Out-of-bounds Write in Facebook Hermes npm · hermes-engine 2020-09-09 critical9.8 CVE-2020-1911 Access of Resource Using Incompatible Type in Facebook Hermes npm · hermes-engine 2020-09-04 critical9.8 CVE-2020-1897 A use-after-free is possible due to an error in lifetime management in the request adaptor when a malicious client invokes request error handling in a specific… facebook · proxygen 2020-05-18 high7.8 CVE-2020-1895 A large heap overflow could occur in Instagram for Android when attempting to upload an image with specially crafted dimensions. facebook · instagram 2020-04-09 high7.5 CVE-2019-11939 Golang Facebook Thrift servers would not error upon receiving messages declaring containers of sizes larger than the payload. go · github.com/facebook/fbthrift 2020-03-18 high7.5 CVE-2019-3553 C++ Facebook Thrift servers would not error upon receiving messages declaring containers of sizes larger than the payload. facebook · thrift 2020-03-10

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.