CVE-2022-39210 json
Access to internal files of the Nextcloud Android app
published 4y ago modified 2mo ago also BIT-nextcloud-2022-39210 , EUVD-2022-41749 , GHSA-vw2w-gpcv-v39f
- cvss
- 3.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
Nextcloud android is the official Android client for the Nextcloud home server platform. Internal paths to the Nextcloud Android app files are not properly protected. As a result access to internal files of the from within the Nextcloud Android app is possible. This may lead to a leak of sensitive information in some cases. It is recommended that the Nextcloud Android app is upgraded to 3.21.0. There are no known workarounds for this issue.
Patch / fix
Is CVE-2022-39210 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.2 | CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | nextcloud | <3.21.0 |
3.21.0 |
Affected products
- nextcloud security-advisories
Classification
References
-
github.com
/nextcloud/android/pull/10544
patch, third-party-advisory, advisory
-
github.com
/nextcloud/security-advisories/security/advisories/GHSA-vw2w-gpcv-v39f
third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39210
web
Sources
- CVE List CVE-2022-39210
- NVD CVE-2022-39210
- OSV BIT-nextcloud-2022-39210
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.