NetSight

Security Dashboard

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

Reset
92 matching advisories · page 2 of 4Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2024-23347 Prior to v176, when opening a new project Meta Spark Studio would execute scripts defined inside of a package.json file included as part of that project. facebook · meta_spark_studio 2024-01-16 high7.5 CVE-2023-49062 Katran could disclose non-initialized kernel memory as part of an IP header. facebook · katran 2023-11-28 high7.5 CVE-2023-46352 In the module "Pixel Plus: Events + CAPI + Pixel Catalog for Facebook Module" (facebookconversiontrackingplus) up to version 2.4.9 from Smart Modules for Prest… smartmodules · facebookconversiontrackingplus 2023-11-02 high7.6 GHSA-86q5-qcjc-7pv4 Presto JDBC Server-Side Request Forgery by nextUri maven · com.facebook.presto:presto-jdbc 2023-10-03 high7.6 GHSA-xm7x-f3w2-4hjm Presto JDBC Server-Side Request Forgery by redirect maven · com.facebook.presto:presto-jdbc 2023-10-03 high7.5 CVE-2023-24833 A use-after-free in BigIntPrimitive addition in Hermes prior to commit a6dcafe6ded8e61658b40f5699878cd19a481f80 could have been used by an attacker to leak raw… facebook · hermes 2023-05-18 high7.5 CVE-2023-24832 A null pointer dereference bug in Hermes prior to commit 5cae9f72975cf0e5a62b27fdd8b01f103e198708 could have been used by an attacker to crash an Hermes runtim… facebook · hermes 2023-05-18 high7.5 CVE-2023-23759 There is a vulnerability in the fizz library prior to v2023.01.30.00 where a CHECK failure can be triggered remotely. facebook · fizz 2023-05-18 high7.5 CVE-2022-4899 zstd vulnerable to buffer overrun swift · github.com/facebook/zstd, pip · zstd 2023-03-31 high7.5 CVE-2022-27810 It was possible to trigger an infinite recursion condition in the error handler when Hermes executed specific maliciously formed JavaScript. facebook · hermes 2022-10-06 high8.5 CVE-2022-23626 m1k1o/blog is a lightweight self-hosted facebook-styled PHP blog. blog_project · blog 2022-02-08 high8.1 CVE-2019-3556 HHVM supports the use of an "admin" server which accepts administrative requests over HTTP. facebook · hhvm 2021-10-26 high8.4 CVE-2021-39207 Deserialization of Untrusted Data in parlai pip · parlai 2021-09-10 high7.5 CVE-2020-1920 Regular expression denial of service in react-native npm · react-native 2021-06-01 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 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 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 high7.5 CVE-2020-1915 Out-of-bounds Read in Facebook Hermes npm · hermes-engine 2020-10-26 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 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 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

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.