F5 Njs vulnerabilities

CVE-2022-29369 [HIGH] CWE-754 CVE-2022-29369: Nginx NJS v0.7.2 was discovered to contain a segmentation violation via njs_lvlhsh_bucket_find at nj Nginx NJS v0.7.2 was discovered to contain a segmentation violation via njs_lvlhsh_bucket_find at njs_lvlhsh.c.

CVE-2022-28049 [MEDIUM] CWE-476 CVE-2022-28049: NGINX NJS 0.7.2 was discovered to contain a NULL pointer dereference via the component njs_vmcode_ar NGINX NJS 0.7.2 was discovered to contain a NULL pointer dereference via the component njs_vmcode_array at /src/njs_vmcode.c.

CVE-2022-27007 [CRITICAL] CWE-416 CVE-2022-27007: nginx njs 0.7.2 is affected suffers from Use-after-free in njs_function_frame_alloc() when it try to nginx njs 0.7.2 is affected suffers from Use-after-free in njs_function_frame_alloc() when it try to invoke from a restored frame saved with njs_function_frame_save().

CVE-2022-27008 [HIGH] CWE-120 CVE-2022-27008: nginx njs 0.7.2 is vulnerable to Buffer Overflow. Type confused in Array.prototype.concat() when a s nginx njs 0.7.2 is vulnerable to Buffer Overflow. Type confused in Array.prototype.concat() when a slow array appended element is fast array.

CVE-2021-46463 [CRITICAL] CWE-843 CVE-2021-46463: njs through 0.7.1, used in NGINX, was discovered to contain a control flow hijack caused by a Type C njs through 0.7.1, used in NGINX, was discovered to contain a control flow hijack caused by a Type Confusion vulnerability in njs_promise_perform_then().

CVE-2022-25139 [CRITICAL] CWE-416 CVE-2022-25139: njs through 0.7.0, used in NGINX, was discovered to contain a heap use-after-free in njs_await_fulfi njs through 0.7.0, used in NGINX, was discovered to contain a heap use-after-free in njs_await_fulfilled.

CVE-2021-46462 [HIGH] CVE-2021-46462: njs through 0.7.1, used in NGINX, was discovered to contain a segmentation violation via njs_object_ njs through 0.7.1, used in NGINX, was discovered to contain a segmentation violation via njs_object_set_prototype in /src/njs_object.c.

CVE-2020-24346 [HIGH] CWE-416 CVE-2020-24346: njs through 0.4.3, used in NGINX, has a use-after-free in njs_json_parse_iterator_call in njs_json.c njs through 0.4.3, used in NGINX, has a use-after-free in njs_json_parse_iterator_call in njs_json.c.

CVE-2020-24347 [MEDIUM] CWE-125 CVE-2020-24347: njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_lvlhsh_level_find in njs_lvlhsh.c njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_lvlhsh_level_find in njs_lvlhsh.c.

CVE-2020-24348 [MEDIUM] CWE-125 CVE-2020-24348: njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_js njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.

CVE-2020-24349 [MEDIUM] CWE-416 CVE-2020-24349: njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. N njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.

CVE-2019-13617 [MEDIUM] CWE-125 CVE-2019-13617: njs through 0.3.3, used in NGINX, has a heap-based buffer over-read in nxt_vsprintf in nxt/nxt_sprin njs through 0.3.3, used in NGINX, has a heap-based buffer over-read in nxt_vsprintf in nxt/nxt_sprintf.c during error handling, as demonstrated by an njs_regexp_literal call that leads to an njs_parser_lexer_error call and then an njs_parser_scope_error call.

CVE-2019-13067 [CRITICAL] CVE-2019-13067: njs through 0.3.3, used in NGINX, has a buffer over-read in nxt_utf8_decode in nxt/nxt_utf8.c. This njs through 0.3.3, used in NGINX, has a buffer over-read in nxt_utf8_decode in nxt/nxt_utf8.c. This issue occurs after the fix for CVE-2019-12207 is in place.

CVE-2019-12207 [CRITICAL] CWE-125 CVE-2019-12207: njs through 0.3.1, used in NGINX, has a heap-based buffer over-read in nxt_utf8_decode in nxt/nxt_ut njs through 0.3.1, used in NGINX, has a heap-based buffer over-read in nxt_utf8_decode in nxt/nxt_utf8.c.

CVE-2019-12206 [CRITICAL] CWE-787 CVE-2019-12206: njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in nxt_utf8_encode in nxt_utf8.c. njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in nxt_utf8_encode in nxt_utf8.c.

CVE-2019-12208 [CRITICAL] CWE-787 CVE-2019-12208: njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in njs_function_native_call in nj njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in njs_function_native_call in njs/njs_function.c.

CVE-2019-11839 [CRITICAL] CWE-787 CVE-2019-11839: njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in Array.prototype.push after a r njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in Array.prototype.push after a resize, related to njs_array_prototype_push in njs/njs_array.c, because of njs_array_expand size mishandling.

CVE-2019-11838 [CRITICAL] CWE-787 CVE-2019-11838: njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in Array.prototype.splice after a njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in Array.prototype.splice after a resize, related to njs_array_prototype_splice in njs/njs_array.c, because of njs_array_expand size mishandling.

CVE-2019-11837 [HIGH] CWE-189 CVE-2019-11837: njs through 0.3.1, used in NGINX, has a segmentation fault in String.prototype.toBytes for negative njs through 0.3.1, used in NGINX, has a segmentation fault in String.prototype.toBytes for negative arguments, related to nxt_utf8_next in nxt/nxt_utf8.h and njs_string_offset in njs/njs_string.c.