File path disclosure via verbatim exception responses
Published Oct 25, 2021 · Updated Aug 4, 2024
Path disclosure in Nextcloud Richdocuments before 3.8.6 and 4.0.0 through 4.2.2 allows remote authenticated users to read shared-file paths. Richdocuments controllers returned caught exception messages verbatim in error responses instead of replacing them with generic messages, exposing the server-side path embedded in a shared-file exception. A low-privileged user must trigger an error while interacting with a shared file, and the resulting disclosure is limited to its server-side path.
Summary
What happened
Path disclosure in Nextcloud Richdocuments before 3.8.6 and 4.0.0 through 4.2.2 allows remote authenticated users to read shared-file paths. Richdocuments controllers returned caught exception messages verbatim in error responses instead of replacing them with generic messages, exposing the server-side path embedded in a shared-file exception. A low-privileged user must trigger an error while interacting with a shared file, and the resulting disclosure is limited to its server-side path.
The record
- CVE
- CVE-2021-39223
- Published
- Oct 25, 2021
- Updated
- Aug 4, 2024
- Vendor
- Nextcloud GmbH
- Product
- Nextcloud Security Advisories
- Classifications
- CWE-200, T1083
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 25, 2021CVE 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.8.6,
- Affected versionversion=>= 4.0.0, < 4.2.3
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