{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24069 exists.","fix":"No fix has been published for CVE-2023-24069 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-24069 is a low-severity vulnerability in n/a, published on 23 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-24069 and fix it if it is affected.\n\nWhat it is: CVE-2023-24069 is a low-severity vulnerability in n/a, published on 23 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24069 exists.\n\nAffected product: n/a. 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-2023-24069/ (Markdown: https://insights.sbomify.com/CVE-2023-24069/index.md)","id":"CVE-2023-24069","markdown":"https://insights.sbomify.com/CVE-2023-24069/index.md","name":"CVE-2023-24069","record":{"aliases":["GHSA-2cqm-w497-9r99"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Signal Desktop","requires_auth":"low_privilege","summary":"An attacker with local filesystem access can recover sensitive message attachments from Signal Desktop's cache directory, even after deletion.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"signal-desktop","vendor":"signal"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Signal Desktop before 6.2.0 on Windows, Linux, and macOS allows an attacker to obtain potentially sensitive attachments sent in messages from the attachments.noindex directory. Cached attachments are not effectively cleared. In some cases, even after a self-initiated file deletion, an attacker can still recover the file if it was previously replied to in a conversation. (Local filesystem access is needed by the attacker.) NOTE: the vendor disputes the relevance of this finding because the product is not intended to protect against adversaries with this degree of local access.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2023-24069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2023-24070"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2023-24068"},"products":["n/a"],"published":"2023-01-23","related":[{"cvss_score":7.8,"headline":"Missing authorization in n/a","id":"CVE-2023-24068","kev_date_added":null,"published":"2023-01-23"},{"cvss_score":7.3,"headline":"Privilege escalation in n/a","id":"CVE-2019-19954","kev_date_added":null,"published":"2019-12-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-11101","kev_date_added":null,"published":"2018-05-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-10994","kev_date_added":null,"published":"2018-05-14"},{"cvss_score":4,"headline":"Information disclosure in n/a","id":"CVE-2018-14023","kev_date_added":null,"published":"2018-08-20"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"An attacker with local filesystem access can recover sensitive message attachments from Signal Desktop's cache directory, even after deletion.","url":"https://insights.sbomify.com/CVE-2023-24069/"}