NetSight

Security Dashboard

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

Reset
153 matching advisories · page 4 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2021-46532 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via exec_expr at src/mjs_exec.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46531 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via /usr/local/bin/mjs+0x8d28e. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46530 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_execute at src/mjs_exec.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46529 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via /usr/local/bin/mjs+0x8814e. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46528 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via /usr/local/bin/mjs+0x5361e. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46527 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via mjs_get_cstring at src/mjs_string.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46526 Cesanta MJS v2.20.0 was discovered to contain a global buffer overflow via snquote at src/mjs_json.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46525 Cesanta MJS v2.20.0 was discovered to contain a heap-use-after-free via mjs_apply at src/mjs_exec.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46524 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via snquote at mjs/src/mjs_json.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46523 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via to_json_or_debug at mjs/src/mjs_json.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46522 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via /usr/lib/x86_64-linux-gnu/libasan.so.4+0xaff53. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46521 Cesanta MJS v2.20.0 was discovered to contain a global buffer overflow via c_vsnprintf at mjs/src/common/str_util.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46520 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via mjs_jprintf at src/mjs_util.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46519 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via mjs_array_length at src/mjs_array.c. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46518 Cesanta MJS v2.20.0 was discovered to contain a heap buffer overflow via mjs_disown at src/mjs_core.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46517 There is an Assertion `mjs_stack_size(&mjs->scopes) > 0' failed at src/mjs_exec.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46516 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_stack_size at mjs/src/mjs_core.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46515 There is an Assertion `mjs_stack_size(&mjs->scopes) >= scopes_len' failed at src/mjs_exec.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46514 There is an Assertion 'ppos != NULL && mjs_is_number(*ppos)' failed at src/mjs_core.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46513 Cesanta MJS v2.20.0 was discovered to contain a global buffer overflow via mjs_mk_string at mjs/src/mjs_string.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46512 Cesanta MJS v2.20.0 was discovered to contain a SEGV vulnerability via mjs_apply at src/mjs_exec.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46511 There is an Assertion `m->len >= sizeof(v)' failed at src/mjs_core.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46510 There is an Assertion `s < mjs->owned_strings.buf + mjs->owned_strings.len' failed at src/mjs_gc.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 high7.8 CVE-2021-46509 Cesanta MJS v2.20.0 was discovered to contain a stack overflow via snquote at mjs/src/mjs_json.c. cesanta · mjs 2022-01-27 medium5.5 CVE-2021-46508 There is an Assertion `i < parts_cnt' failed at src/mjs_bcode.c in Cesanta MJS v2.20.0. cesanta · mjs 2022-01-27 medium5.5 CVE-2020-36375 Stack overflow vulnerability in parse_equality Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. cesanta · mjs 2021-05-28 medium5.5 CVE-2020-36374 Stack overflow vulnerability in parse_comparison Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. cesanta · mjs 2021-05-28 medium5.5 CVE-2020-36373 Stack overflow vulnerability in parse_shifts Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. cesanta · mjs 2021-05-28 medium5.5 CVE-2020-36372 Stack overflow vulnerability in parse_plus_minus Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. cesanta · mjs 2021-05-28 medium5.5 CVE-2020-36371 Stack overflow vulnerability in parse_mul_div_rem Cesanta MJS 1.20.1, allows remote attackers to cause a Denial of Service (DoS) via a crafted file. cesanta · mjs 2021-05-28

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.