{"answers":{"affected":"1 open source package ship an affected version, including nextcloud. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29160 exists.","fix":"Upgrade nextcloud to 3.19.0 or later.","what":"CVE-2022-29160 is a low-severity vulnerability in nextcloud security-advisories, published on 20 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-29160 and fix it if it is affected.\n\nWhat it is: CVE-2022-29160 is a low-severity vulnerability in nextcloud security-advisories, published on 20 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-29160 exists.\n\nAffected packages and fixed versions:\n- nextcloud (Bitnami): affected all versions; fixed in 3.19.0\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-2022-29160/ (Markdown: https://insights.sbomify.com/CVE-2022-29160/index.md)","id":"CVE-2022-29160","markdown":"https://insights.sbomify.com/CVE-2022-29160/index.md","name":"CVE-2022-29160","record":{"aliases":["BIT-nextcloud-2022-29160","GHSA-xcj9-3jch-qr2r"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Nextcloud Android client","requires_auth":"low_privilege","summary":"Sensitive tokens and user data remain accessible after account deletion in the Nextcloud Android app, potentially exposing private information.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"nextcloud","vendor":"nextcloud"}],"cvss":{"score":2.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-459","name":"Incomplete Cleanup"},{"id":"CWE-284","name":"Improper Access Control"}],"description":"Nextcloud Android is the Android client for Nextcloud, a self-hosted productivity platform. Prior to version 3.19.0, sensitive tokens, images, and user related details exist after deletion of a user account. This could result in misuse of the former account holder's information. Nextcloud Android version 3.19.0 contains a patch for this issue. There are no known workarounds available.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Sensitive files/data exist after deletion of user account in Nextcloud Android","id":"CVE-2022-29160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":1,"n_references":3,"next":{"headline":"Crypto script service uses hashing algorithm SHA1 with RSA for certificate signature in xwiki-platform","id":"CVE-2022-29161"},"packages":[{"ecosystem":"Bitnami","fixed":["3.19.0"],"introduced":["0"],"last_affected":[],"package":"nextcloud","purl":"pkg:bitnami/nextcloud","source":"BIT-nextcloud-2022-29160"}],"prev":{"headline":"Possibility for anyone to add a stack with existing tasks on anyone's board in Nextcloud Deck","id":"CVE-2022-29159"},"products":["security-advisories"],"published":"2022-05-20","related":[{"cvss_score":9.8,"headline":"SQL injection in com.nextcloud.client","id":"CVE-2019-5454","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":7.5,"headline":"SQL Injection in FileContentProvider (GHSL-2021-1007)","id":"CVE-2021-43863","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":6.8,"headline":"Cross-site scripting in com.nextcloud.client","id":"CVE-2019-5450","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":6.8,"headline":"Auth bypass in com.nextcloud.client","id":"CVE-2019-5455","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":6.5,"headline":"Information disclosure in Nextcloud Android App (com.nextcloud.client)","id":"CVE-2021-22905","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":6.5,"headline":"Information disclosure in Nextcloud iOS app (it.twsweb.Nextcloud)","id":"CVE-2021-22912","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":6.1,"headline":"Auth bypass in Nextcloud Android","id":"CVE-2019-15615","kev_date_added":null,"published":"2020-02-04"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["nextcloud"]},"summary":"Sensitive tokens and user data remain accessible after account deletion in the Nextcloud Android app, potentially exposing private information.","url":"https://insights.sbomify.com/CVE-2022-29160/"}