Memory Corruption

Every one of the 44 is a mark on the map. Named now: 1 to 26, most at risk first.

1. JerryScript commit 4e58ccf68070671e1fff5cd6673f0c1d5b80b166 is affected by: Buffer Overflow. The impact is: denial of service and possibly arbitrary code execution. The component…CVE-2019-1010176JerryScript · 2.5% likely

   CWE-787

2. 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 c…CVE-2017-9250Jerryscript · 2.5% likely

   CWE-476

3. Buffer Overflow vulnerability in JerryScript version 3.0, allows remote attackers to execute arbitrary code via ecma_stringbuilder_append_raw component at /jerry-core/ecma/base/ec…CVE-2023-36109Jerryscript · 2.4% likely

   CWE-120

4. 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 pointer dereference and…CVE-2020-13649Jerryscript · 2.2% likely

   CWE-476

5. 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 f…CVE-2017-14749Jerryscript · 2.1% likely

   CWE-119

6. 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"); payl…CVE-2017-18212Jerryscript · 1.8% likely

   CWE-125

7. A buffer overflow in ecma_builtin_typedarray_prototype_filter() in JerryScript version fe3a5c0 allows an attacker to construct a fake object or a fake arraybuffer with unlimited s…CVE-2021-42863Jerryscript · 1.7% likely

   CWE-120

8. 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_c…CVE-2018-11419Jerryscript · 1.5% likely

   CWE-125

9. 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_par…CVE-2018-11418Jerryscript · 1.5% likely

   CWE-125

10. Buffer Overflwo vulnerability in JerryScript Project jerryscript v.3.0.0 allows a remote attacker to execute arbitrary code via the scanner_is_context_needed component in js-scann…CVE-2023-38961Jerryscript · 1.5% likely

    CWE-787

11. There is a heap-buffer-overflow at re-parser.c in re_parse_char_escape in JerryScript 2.2.0.CVE-2020-23323Jerryscript · 1.3% likely

    CWE-787

12. 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-23321Jerryscript · 1.3% likely

    CWE-787

13. There is a heap-buffer-overflow at jmem-poolman.c:165 in jmem_pools_collect_empty in JerryScript 2.2.0.CVE-2020-23303Jerryscript · 1.3% likely

    CWE-787

14. There is a stack-overflow at ecma-regexp-object.c:535 in ecma_regexp_match in JerryScript 2.2.0.CVE-2020-23306Jerryscript · 1.3% likely

    CWE-787

15. An issue was discovered in ecma/operations/ecma-container-object.c in JerryScript 2.2.0. Operations with key/value pairs did not consider the case where garbage collection is trig…CVE-2020-14163Jerryscript · 1.3% likely

    CWE-125

16. There is a heap-use-after-free at ecma-helpers-string.c:772 in ecma_ref_ecma_string in JerryScript 2.2.0CVE-2020-23302Jerryscript · 1.3% likely

    CWE-416

17. A Heap-based Buffer Overflow vulnerability exists in JerryScript 2.4.0 and prior versions via an out-of-bounds read in parser_parse_for_statement_start in the js-parser-statm.c fi…CVE-2021-43453Jerryscript · 1.3% likely

    CWE-125

18. In JerryScript 2.3.0, there is an out-of-bounds read in main_print_unhandled_exception in the main-utils.c file.CVE-2020-29657Jerryscript · 1.2% likely

    CWE-125

19. Buffer overflow vulnerability in file ecma-builtin-array-prototype.c:909 in function ecma_builtin_array_prototype_object_slice in Jerryscript before commit e1ce7dd7271288be8c0c813…CVE-2021-41751Jerryscript · 1.2% likely

    CWE-120

20. An issue was discovered in JerryScript commit a6ab5e9. There is an Use-After-Free in lexer_compare_identifier_to_string in js-lexer.c file.CVE-2021-46170Jerryscript · 1.2% likely

    CWE-416

21. An issue was discovered in JerryScript 2.4.0. There is a heap-buffer-overflow in lexer_parse_number in js-lexer.c file.CVE-2021-26195Jerryscript · 1.1% likely

    CWE-787

22. JerryScript version Tested on commit f86d7459d195c8ba58479d1861b0cc726c8b3793. Analysing history it seems that the issue has been present since commit 64a340ffeb8809b2b66bbe32fd44…CVE-2018-1000636Jerryscript · 1.1% likely

    CWE-476

23. 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-2021-26194Jerryscript · 0.9% likely

    CWE-416

24. An issue was discovered in JerryScript 2.4.0. There is a heap-use-after-free in ecma_bytecode_ref in ecma-helpers.c file.CVE-2021-26199Jerryscript · 0.9% likely

    CWE-416

25. Jerryscript 3.0.0 was discovered to contain a heap-buffer-overflow via ecma_utf8_string_to_number_by_radix in /jerry-core/ecma/base/ecma-helpers-conversion.c.CVE-2022-22895Jerryscript · 0.8% likely

    CWE-787

26. 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-lim…CVE-2020-24345Jerryscript · 0.8% likely

    CWE-787

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.