Unauthenticated account creation via missing API authorization
Published Mar 27, 2020 · Updated Aug 4, 2024
Improper access control in F5 NGINX Controller before 3.2.0 allows remote attackers to create unprivileged accounts through its API. The Controller API account-creation path accepts unauthenticated requests instead of enforcing authentication before provisioning a user. Network access to the API is required; a created account can upload a new license but cannot view or modify other components.
Summary
What happened
Improper access control in F5 NGINX Controller before 3.2.0 allows remote attackers to create unprivileged accounts through its API. The Controller API account-creation path accepts unauthenticated requests instead of enforcing authentication before provisioning a user. Network access to the API is required; a created account can upload a new license but cannot view or modify other components.
The record
- CVE
- CVE-2020-5863
- Published
- Mar 27, 2020
- Updated
- Aug 4, 2024
- Vendor
- F5 Networks
- Product
- NGINX Controller
- Classifications
- T1136
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0-3.1.0, 2.0.0-2.9.0, 1.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo