CVE-2022-24906 json
Error in deleting deck cards attachment reveals the full application path in Nextcloud Deck
published 4y ago modified 4mo ago also EUVD-2022-29663
- cvss
- 3.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
Nextcloud Deck is a Kanban-style project & personal management tool for Nextcloud, similar to Trello. The full path of the application is exposed to unauthorized users. It is recommended that the Nextcloud Deck app is upgraded to 1.2.11, 1.4.6, or 1.5.4. There is no workaround available.
Patch / fix
Is CVE-2022-24906 in your stack? 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
1.08% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/nextcloud/security-advisories/security/advisories/GHSA-hx9w-xfrg-2qvp referenced PoC, tagged "exploit" by a source, unverified
- hackerone.com https://hackerone.com/reports/1354334 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- nextcloud security-advisories
Classification
References
-
github.com
/nextcloud/deck/pull/3384
issue-tracking, patch, third-party-advisory
-
github.com
/nextcloud/security-advisories/security/advisories/GHSA-hx9w-xfrg-2qvp
exploit, issue-tracking, third-party-advisory
-
hackerone.com
/reports/1354334
exploit, issue-tracking, third-party-advisory
Sources
- CVE List CVE-2022-24906
- NVD CVE-2022-24906
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.