Unauthenticated SFCB access via crafted network request
Published Jul 13, 2021 · Updated Aug 3, 2024
Authentication bypass in VMware ESXi 6.5 through 7.0 allows remote attackers to access SFCB through crafted requests to port 5989. VMware has not disclosed which SFCB authentication check mishandles the crafted request or what request element triggers the bypass. Network access to port 5989 and a running SFCB service, which is disabled by default, are required; the bounded impact is access past SFCB authentication.
Summary
What happened
Authentication bypass in VMware ESXi 6.5 through 7.0 allows remote attackers to access SFCB through crafted requests to port 5989. VMware has not disclosed which SFCB authentication check mishandles the crafted request or what request element triggers the bypass. Network access to port 5989 and a running SFCB service, which is disabled by default, are required; the bounded impact is access past SFCB authentication.
The record
- CVE
- CVE-2021-21994
- Published
- Jul 13, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-287, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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