CVE-2020-8236
First published: Fri Oct 30 2020(Updated: )
A wrong configuration in Nextcloud Server 19.0.1 incorrectly made the user feel the passwordless WebAuthn is also a two factor verification by asking for the PIN of the passwordless WebAuthn but not verifying it.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Nextcloud Server | <19.0.2 |
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-8236?
CVE-2020-8236 is classified as a medium severity vulnerability due to its potential to mislead users about the security of the passwordless WebAuthn implementation.
How do I fix CVE-2020-8236?
To resolve CVE-2020-8236, upgrade Nextcloud Server to version 19.0.2 or later which addresses the misconfiguration.
What are the implications of CVE-2020-8236?
The implications of CVE-2020-8236 include the possibility that users may incorrectly assume their passwordless authentication method is secure when it actually requires additional verification.
Who is affected by CVE-2020-8236?
Users of Nextcloud Server versions prior to 19.0.2 are affected by CVE-2020-8236.
Does CVE-2020-8236 impact two-factor authentication?
Yes, CVE-2020-8236 affects the user experience related to two-factor authentication by not properly verifying the WebAuthn PIN.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/author
- agent/weakness
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/nextcloud
- canonical/nextcloud server