Nginx Controller vulnerabilitiesRanked by how likely they are to be used.
Nginx Controller is made by F5. We track 18 published vulnerabilities listed under that exact name, across 31 versions. None of them is on the list of flaws known to be exploited today. F5 lists newer releases under their own names, such as Nginx Controller API Management, so check those pages too.
We keep watching the known-exploited list.
Is Nginx Controller listed under other names? Yes.
F5 also lists Nginx Controller under more specific names, such as Nginx Controller API Management. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Nginx Controller vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Nginx Controller's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Nginx Controller 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.
- 1.7%CVE-2020-27730Critical
In versions 3.0.0-3.9.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller Agent does not use absolute paths when calling system utilities.
- 1.5%CVE-2020-5901Critical
In NGINX Controller 3.3.0-3.4.0, undisclosed API endpoints may allow for a reflected Cross Site Scripting (XSS) attack.
- 1.2%CVE-2020-5910High
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the Neural Autonomic Transport System (NATS) messaging services in use by the NGINX Controller do not require any form of authentication, so any successful connection...
- 1.2%CVE-2020-5863High
In NGINX Controller versions prior to 3.2.0, an unauthenticated attacker with network access to the Controller API can create unprivileged user accounts.
- 1.1%CVE-2020-5864High
In versions of NGINX Controller prior to 3.2.0, communication between NGINX Controller and NGINX Plus instances skip TLS verification by default.
- 1.0%CVE-2020-5894High
On versions 3.0.0-3.3.0, the NGINX Controller webserver does not invalidate the server-side session token after users log out.
- 1.0%CVE-2020-5911High
In versions 3.0.0-3.5.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller installer starts the download of Kubernetes packages from an HTTP URL On Debian/Ubuntu system.
- 0.5%CVE-2021-23018High
Intra-cluster communication does not use TLS.
- 0.5%CVE-2020-5867High
In versions prior to 3.3.0, the NGINX Controller Agent installer script 'install.sh' uses HTTP instead of HTTPS to check and install packages
- 0.5%CVE-2020-5900High
In versions 3.0.0-3.4.0, 2.0.0-2.9.0, and 1.0.1, there is insufficient cross-site request forgery (CSRF) protections for the NGINX Controller user interface.
Running Nginx Controller? 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
In versions 3.0.0-3.9.0, 2.0.0-2.9.0, and 1.0.1, the NGINX Controller Agent does not use absolute paths when calling system utilities.
- Matched to
- Nginx Controller 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 18 published vulnerabilities listed under the name Nginx Controller, across 31 versions.
None of Nginx Controller's vulnerabilities is on the list of flaws known to be exploited today.
F5 also lists Nginx Controller under more specific names, such as Nginx Controller API Management. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Nginx Controller. 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.