{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-39223 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-39223 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-39223 is a medium-severity vulnerability in nextcloud security-advisories, published on 25 Oct 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-39223 and fix it if it is affected.\n\nWhat it is: CVE-2021-39223 is a medium-severity vulnerability in nextcloud security-advisories, published on 25 Oct 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-39223 in the wild and no public exploit code.\n\nAffected product: nextcloud security-advisories. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-39223/ (Markdown: https://insights.sbomify.com/CVE-2021-39223/index.md)","id":"CVE-2021-39223","markdown":"https://insights.sbomify.com/CVE-2021-39223/index.md","name":"CVE-2021-39223","record":{"aliases":["GHSA-rjcc-4cgj-6v93"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Nextcloud Richdocuments app","requires_auth":"low_privilege","summary":"An attacker can view full file paths of shared documents due to verbose error messages in the Nextcloud Richdocuments application.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"richdocuments","vendor":"nextcloud"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Nextcloud is an open-source, self-hosted productivity platform. The Nextcloud Richdocuments application prior to versions 3.8.6 and 4.2.3 returned verbatim exception messages to the user. This could result in a full path disclosure on shared files. (e.g. an attacker could see that the file `shared.txt` is located within `/files/$username/Myfolder/Mysubfolder/shared.txt`). It is recommended that the Richdocuments application is upgraded to 3.8.6 or 4.2.3. As a workaround, disable the Richdocuments application in the app settings.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"File path disclosure of shared files in Richdocuments application","id":"CVE-2021-39223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"File path disclosure of shared files in OfficeOnline application","id":"CVE-2021-39224"},"packages":[],"prev":{"headline":"XSS in Talk","id":"CVE-2021-39222"},"products":["security-advisories"],"published":"2021-10-25","related":[{"cvss_score":7.5,"headline":"File Drop can be bypassed using Richdocuments app in nextcloud","id":"CVE-2021-37628","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":6.5,"headline":"Federated editing allows iframing remote servers by default in richdocuments","id":"CVE-2022-31024","kev_date_added":null,"published":"2022-06-02"},{"cvss_score":5.8,"headline":"Document content of files can be obtained through Collabora for files of other users","id":"CVE-2023-25150","kev_date_added":null,"published":"2023-02-08"},{"cvss_score":5.7,"headline":"Secure view can be bypassed by using internal API endpoint in Nextcloud richdocuments","id":"CVE-2023-28645","kev_date_added":null,"published":"2023-03-31"},{"cvss_score":5.3,"headline":"Lack of ratelimit on Richdocuments OCS endpoint in nextcloud","id":"CVE-2021-37629","kev_date_added":null,"published":"2021-09-07"},{"cvss_score":4.3,"headline":"WOPI API not protected by credentials/IP check","id":"CVE-2021-32748","kev_date_added":null,"published":"2021-07-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["nextcloud"]},"summary":"An attacker can view full file paths of shared documents due to verbose error messages in the Nextcloud Richdocuments application.","url":"https://insights.sbomify.com/CVE-2021-39223/"}