Njs vulnerabilitiesRanked by how likely they are to be used.
Njs is made by F5. We track 37 published vulnerabilities in it, across 60 versions. None of them is on the list of flaws known to be exploited today. If you run Njs, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Njs vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Njs's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Njs flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.0%CVE-2019-12206Critical
njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in nxt_utf8_encode in nxt_utf8.c.
- 1.8%CVE-2019-12207Critical
njs through 0.3.1, used in NGINX, has a heap-based buffer over-read in nxt_utf8_decode in nxt/nxt_utf8.c.
- 1.7%CVE-2019-12208Critical
njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in njs_function_native_call in njs/njs_function.c.
- 1.7%CVE-2022-27008High
nginx njs 0.7.2 is vulnerable to Buffer Overflow.
- 1.7%CVE-2022-29379Critical
Nginx NJS v0.7.3 was discovered to contain a stack overflow in the function njs_default_module_loader at /src/njs/src/njs_module.c.
- 1.7%CVE-2021-46462High
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.
- 1.7%CVE-2021-46463Critical
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().
- 1.6%CVE-2019-11839Critical
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.
- 1.6%CVE-2022-25139Critical
njs through 0.7.0, used in NGINX, was discovered to contain a heap use-after-free in njs_await_fulfilled.
- 1.6%CVE-2019-11838Critical
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.
Running Njs? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
njs through 0.3.1, used in NGINX, has a heap-based buffer overflow in nxt_utf8_encode in nxt_utf8.c.
- Matched to
- Njs on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 37 published vulnerabilities listed under the name Njs, across 60 versions.
None of Njs's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Njs. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.