Nextcloud Server DNS pin middleware can be tricked into DNS rebinding allowing SSRF
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 22.2.10.16, 23.0.12.11, 24.0.12.7, 25.0.11, 26.0.6, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Nextcloud Server provides data storage for Nextcloud, an open source cloud platform. Starting in version 25.0.0 and prior to versions 25.0.11, 26.0.6, and 27.1.0 of Nextcloud Server and starting in version 22.0.0 and prior to versions 22.2.10.16, 23.0.12.11, 24.0.12.7, 25.0.11, 26.0.6, and 27.1.0 of Nextcloud Enterprise Server, the DNS pin middleware was vulnerable to DNS rebinding allowing an attacker to perform SSRF as a final result. Nextcloud Server 25.0.11, 26.0.6, and 27.1.0 and Nextcloud Enterprise Server 22.2.10.16, 23.0.12.11, 24.0.12.7, 25.0.11, 26.0.6, and 27.1.0 contain patches for this issue. No known workarounds are available.
Timeline
- CVE published
- Record last updated
Affected versions
- nextcloud security-advisories
From 22.0.0 · fixed in 22.2.10.16; From 23.0.0 · fixed in 23.0.12.11; From 24.0.0 · fixed in 24.0.12.7; From 25.0.0 · fixed in 25.0.11; From 26.0.0 · fixed in 26.0.6; From 27.0.0 · fixed in 27.1.0