CVE-2020-8138: SSRF
First published: Fri Mar 20 2020(Updated: )
A missing check for IPv4 nested inside IPv6 in Nextcloud server < 17.0.1, < 16.0.7, and < 15.0.14 allowed a Server-Side Request Forgery (SSRF) vulnerability when subscribing to a malicious calendar URL.
Credit: support@hackerone.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Nextcloud Server | <15.0.14 | |
| Nextcloud Server | >=16.0.0<16.0.7 | |
| Nextcloud Server | >=17.0.0<17.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-8138?
CVE-2020-8138 has a medium severity rating, indicating that it poses a notable risk.
How do I fix CVE-2020-8138?
To fix CVE-2020-8138, upgrade your Nextcloud server to version 15.0.14, 16.0.7, or 17.0.1 or later.
What systems are affected by CVE-2020-8138?
CVE-2020-8138 affects Nextcloud server versions earlier than 15.0.14, 16.0.7, and 17.0.1.
What type of vulnerability is CVE-2020-8138?
CVE-2020-8138 is classified as a Server-Side Request Forgery (SSRF) vulnerability.
What consequences can arise from CVE-2020-8138?
Exploitation of CVE-2020-8138 can lead to unauthorized access to internal network resources.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/author
- agent/description
- agent/event
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/nextcloud
- canonical/nextcloud server
- version/nextcloud server/16.0.0
- version/nextcloud server/17.0.0