CVE-2020-5899
First published: Wed Jul 01 2020(Updated: )
In NGINX Controller 3.0.0-3.4.0, recovery code required to change a user's password is transmitted and stored in the database in plain text, which allows an attacker who can intercept the database connection or have read access to the database, to request a password reset using the email address of another registered user then retrieve the recovery code.
Credit: f5sirt@f5.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| F5 NGINX Controller API Management | >=3.0.0<=3.4.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2020-5899?
CVE-2020-5899 is classified as a high severity vulnerability due to exposed sensitive information.
How do I fix CVE-2020-5899?
To fix CVE-2020-5899, upgrade NGINX Controller to a version above 3.4.0 where recovery codes are not stored in plain text.
What are the risks associated with CVE-2020-5899?
The risks of CVE-2020-5899 include unauthorized access to user accounts if the database is compromised.
Who is affected by CVE-2020-5899?
Organizations using NGINX Controller versions 3.0.0 to 3.4.0 are affected by CVE-2020-5899.
What types of attacks can exploit CVE-2020-5899?
Attackers can exploit CVE-2020-5899 through database interception or unauthorized database access to gain sensitive information.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/references
- agent/author
- agent/severity
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/f5
- canonical/f5 nginx controller api management
- version/f5 nginx controller api management/3.0.0
- version/f5 nginx controller api management/3.4.0