Search
Total
72 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2021-26194 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 4.3 MEDIUM | 6.5 MEDIUM |
| An issue was discovered in JerryScript 2.4.0. There is a heap-use-after-free in ecma_is_lexical_environment in the ecma-helpers.c file. | |||||
| CVE-2020-23323 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 7.5 HIGH | 9.8 CRITICAL |
| There is a heap-buffer-overflow at re-parser.c in re_parse_char_escape in JerryScript 2.2.0. | |||||
| CVE-2020-23321 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 7.5 HIGH | 9.8 CRITICAL |
| There is a heap-buffer-overflow at lit-strings.c:431 in lit_read_code_unit_from_utf8 in JerryScript 2.2.0. | |||||
| CVE-2020-23310 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 5.0 MEDIUM | 7.5 HIGH |
| 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 JerryScript 2.2.0. | |||||
| CVE-2020-23309 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 5.0 MEDIUM | 7.5 HIGH |
| 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.0. | |||||
| CVE-2020-23308 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 5.0 MEDIUM | 7.5 HIGH |
| 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. | |||||
| CVE-2020-23306 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 7.5 HIGH | 9.8 CRITICAL |
| There is a stack-overflow at ecma-regexp-object.c:535 in ecma_regexp_match in JerryScript 2.2.0. | |||||
| CVE-2020-23303 | 1 Jerryscript | 1 Jerryscript | 2021-06-16 | 7.5 HIGH | 9.8 CRITICAL |
| There is a heap-buffer-overflow at jmem-poolman.c:165 in jmem_pools_collect_empty in JerryScript 2.2.0. | |||||
| CVE-2020-23320 | 1 Jerryscript | 1 Jerryscript | 2021-06-15 | 5.0 MEDIUM | 7.5 HIGH |
| 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. | |||||
| CVE-2020-23302 | 1 Jerryscript | 1 Jerryscript | 2021-06-15 | 7.5 HIGH | 9.8 CRITICAL |
| There is a heap-use-after-free at ecma-helpers-string.c:772 in ecma_ref_ecma_string in JerryScript 2.2.0 | |||||
| CVE-2020-29657 | 1 Jerryscript | 1 Jerryscript | 2020-12-10 | 6.4 MEDIUM | 9.1 CRITICAL |
| In JerryScript 2.3.0, there is an out-of-bounds read in main_print_unhandled_exception in the main-utils.c file. | |||||
| CVE-2017-9250 | 1 Jerryscript | 1 Jerryscript | 2020-10-28 | 5.0 MEDIUM | 7.5 HIGH |
| The lexer_process_char_literal function in jerry-core/parser/js/js-lexer.c in JerryScript 1.0 does not skip memory allocation for empty strings, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via malformed JavaScript source code, related to the jmem_heap_free_block function. | |||||
| CVE-2020-13991 | 1 Jerryscript | 1 Jerryscript | 2020-09-30 | 5.0 MEDIUM | 7.5 HIGH |
| vm/opcodes.c in JerryScript 2.2.0 allows attackers to hijack the flow of control by controlling a register. | |||||
| CVE-2020-24344 | 1 Jerryscript | 1 Jerryscript | 2020-08-19 | 5.8 MEDIUM | 7.1 HIGH |
| JerryScript through 2.3.0 has a (function({a=arguments}){const arguments}) buffer over-read. | |||||
| CVE-2020-24345 | 1 Jerryscript | 1 Jerryscript | 2020-08-14 | 6.8 MEDIUM | 7.8 HIGH |
| ** DISPUTED ** JerryScript through 2.3.0 allows stack consumption via function a(){new new Proxy(a,{})}JSON.parse("[]",a). NOTE: the vendor states that the problem is the lack of the --stack-limit option. | |||||
| CVE-2020-13622 | 1 Jerryscript | 1 Jerryscript | 2020-05-27 | 5.0 MEDIUM | 7.5 HIGH |
| JerryScript 2.2.0 allows attackers to cause a denial of service (assertion failure) because a property key query for a Proxy object returns unintended data. | |||||
| CVE-2020-13623 | 1 Jerryscript | 1 Jerryscript | 2020-05-27 | 5.0 MEDIUM | 7.5 HIGH |
| JerryScript 2.2.0 allows attackers to cause a denial of service (stack consumption) via a proxy operation. | |||||
| CVE-2017-18212 | 1 Jerryscript | 1 Jerryscript | 2019-10-03 | 7.5 HIGH | 9.8 CRITICAL |
| An issue was discovered in JerryScript 1.0. There is a heap-based buffer over-read in the lit_read_code_unit_from_hex function in lit/lit-char-helpers.c via a RegExp("[\x0"); payload. | |||||
| CVE-2018-11419 | 1 Jerryscript | 1 Jerryscript | 2019-10-03 | 7.5 HIGH | 9.8 CRITICAL |
| An issue was discovered in JerryScript 1.0. There is a heap-based buffer over-read in the lit_read_code_unit_from_hex function via a RegExp("[\\u0") payload, related to re_parse_char_class in parser/regexp/re-parser.c. | |||||
| CVE-2018-11418 | 1 Jerryscript | 1 Jerryscript | 2019-10-03 | 7.5 HIGH | 9.8 CRITICAL |
| An issue was discovered in JerryScript 1.0. There is a heap-based buffer over-read in the lit_read_code_unit_from_utf8 function via a RegExp("[\\u0020") payload, related to re_parse_char_class in parser/regexp/re-parser.c. | |||||
| CVE-2018-1000636 | 1 Jerryscript | 1 Jerryscript | 2018-11-07 | 4.3 MEDIUM | 6.5 MEDIUM |
| JerryScript version Tested on commit f86d7459d195c8ba58479d1861b0cc726c8b3793. Analysing history it seems that the issue has been present since commit 64a340ffeb8809b2b66bbe32fd443a8b79fdd860 contains a CWE-476: NULL Pointer Dereference vulnerability in Triggering undefined behavior at jerry-core/ecma/builtin-objects/typedarray/ecma-builtin-typedarray-prototype.c:598 (passing NULL to memcpy as 2nd argument) results in null pointer dereference (segfault) at jerry-core/jmem/jmem-heap.c:463 that can result in Crash due to segmentation fault. This attack appear to be exploitable via The victim must execute specially crafted javascript code. This vulnerability appears to have been fixed in after commit 87897849f6879df10e8ad68a41bf8cf507edf710. | |||||
| CVE-2017-14749 | 1 Jerryscript | 1 Jerryscript | 2017-10-06 | 6.8 MEDIUM | 7.8 HIGH |
| JerryScript 1.0 allows remote attackers to cause a denial of service (jmem_heap_alloc_block_internal heap memory corruption) or possibly execute arbitrary code via a crafted .js file, because unrecognized \ characters cause incorrect 0x00 characters in bytecode.literal data. | |||||