NetSight

Security Dashboard

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

Reset
98 matching advisories · page 3 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2021-46337 There is an Assertion 'page_p != NULL' failed at /parser/js/js-parser-mem.c(parser_list_get) in JerryScript 3.0.0. jerryscript · jerryscript 2022-01-20 medium5.5 CVE-2021-46336 There is an Assertion 'opts & PARSER_CLASS_LITERAL_CTOR_PRESENT' failed at /parser/js/js-parser-expr.c(parser_parse_class_body) in JerryScript 3.0.0. jerryscript · jerryscript 2022-01-20 high7.5 CVE-2021-46170 An issue was discovered in JerryScript commit a6ab5e9. jerryscript · jerryscript 2022-01-14 medium6.5 CVE-2021-26199 An issue was discovered in JerryScript 2.4.0. jerryscript · jerryscript 2021-06-10 medium6.5 CVE-2021-26198 An issue was discovered in JerryScript 2.4.0. jerryscript · jerryscript 2021-06-10 medium6.5 CVE-2021-26197 An issue was discovered in JerryScript 2.4.0. jerryscript · jerryscript 2021-06-10 high8.8 CVE-2021-26195 An issue was discovered in JerryScript 2.4.0. jerryscript · jerryscript 2021-06-10 medium6.5 CVE-2021-26194 An issue was discovered in JerryScript 2.4.0. jerryscript · jerryscript 2021-06-10 critical9.8 CVE-2020-23323 There is a heap-buffer-overflow at re-parser.c in re_parse_char_escape in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23322 There is an Assertion in 'context_p->token.type == LEXER_RIGHT_BRACE || context_p->token.type == LEXER_ASSIGN || context_p->token.type == LEXER_COMMA' in parse… jerryscript · jerryscript 2021-06-10 critical9.8 CVE-2020-23321 There is a heap-buffer-overflow at lit-strings.c:431 in lit_read_code_unit_from_utf8 in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23320 There is an Assertion in 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' in parser_parse_function_arguments in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23319 There is an Assertion in '(flags >> CBC_STACK_ADJUST_SHIFT) >= CBC_STACK_ADJUST_BASE || (CBC_STACK_ADJUST_BASE - (flags >> CBC_STACK_ADJUST_SHIFT)) <= context_… jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23314 There is an Assertion 'block_found' failed at js-parser-statm.c:2003 parser_parse_try_statement_end in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23313 There is an Assertion 'scope_stack_p > context_p->scope_stack_p' failed at js-scanner-util.c:2510 in scanner_literal_is_created in JerryScript 2.2.0 jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23312 There is an Assertion 'context.status_flags & PARSER_SCANNING_SUCCESSFUL' failed at js-parser.c:2185 in parser_parse_source in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23311 There is an Assertion 'context_p->token.type == LEXER_RIGHT_BRACE || context_p->token.type == LEXER_ASSIGN || context_p->token.type == LEXER_COMMA' failed at j… jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23310 There is an Assertion 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed at js-parser-statm.c:733 in parser_parse_function_statement in Jer… jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23309 There is an Assertion 'context_p->stack_depth == context_p->context_stack_depth' failed at js-parser-statm.c:2756 in parser_parse_statements in JerryScript 2.2… jerryscript · jerryscript 2021-06-10 high7.5 CVE-2020-23308 There is an Assertion 'context_p->stack_top_uint8 == LEXER_EXPRESSION_START' at js-parser-expr.c:3565 in parser_parse_expression in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 critical9.8 CVE-2020-23306 There is a stack-overflow at ecma-regexp-object.c:535 in ecma_regexp_match in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 critical9.8 CVE-2020-23303 There is a heap-buffer-overflow at jmem-poolman.c:165 in jmem_pools_collect_empty in JerryScript 2.2.0. jerryscript · jerryscript 2021-06-10 critical9.8 CVE-2020-23302 There is a heap-use-after-free at ecma-helpers-string.c:772 in ecma_ref_ecma_string in JerryScript 2.2.0 jerryscript · jerryscript 2021-06-10 critical9.1 CVE-2020-29657 In JerryScript 2.3.0, there is an out-of-bounds read in main_print_unhandled_exception in the main-utils.c file. jerryscript · jerryscript 2020-12-09 high7.5 CVE-2020-13991 vm/opcodes.c in JerryScript 2.2.0 allows attackers to hijack the flow of control by controlling a register. jerryscript · jerryscript 2020-09-24 high7.8 CVE-2020-24345 JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse("[]",a). jerryscript · jerryscript 2020-08-13 high7.1 CVE-2020-24344 JerryScript through 2.3.0 has a (function({a=arguments}){const arguments}) buffer over-read. jerryscript · jerryscript 2020-08-13 high7.5 CVE-2020-14163 An issue was discovered in ecma/operations/ecma-container-object.c in JerryScript 2.2.0. jerryscript · jerryscript 2020-06-15 high7.5 CVE-2020-13649 parser/js/js-scanner.c in JerryScript 2.2.0 mishandles errors during certain out-of-memory conditions, as demonstrated by a scanner_reverse_info_list NULL poin… jerryscript · jerryscript 2020-05-28 high7.5 CVE-2020-13623 JerryScript 2.2.0 allows attackers to cause a denial of service (stack consumption) via a proxy operation. jerryscript · jerryscript 2020-05-27

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.