{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-3988 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-3988 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-3988 is a low-severity vulnerability in Signal, published on 10 Dec 2018. 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-2018-3988 and fix it if it is affected.\n\nWhat it is: CVE-2018-3988 is a low-severity vulnerability in Signal, published on 10 Dec 2018. 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: There is no known exploitation of CVE-2018-3988 in the wild and no public exploit code.\n\nAffected product: Signal. 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-2018-3988/ (Markdown: https://insights.sbomify.com/CVE-2018-3988/index.md)","id":"CVE-2018-3988","markdown":"https://insights.sbomify.com/CVE-2018-3988/index.md","name":"CVE-2018-3988","record":{"aliases":["GHSA-f287-vf22-3v2c"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Signal Android app","requires_auth":"none","summary":"Signal for Android may leak private photos to other apps via cache when using disappearing messages, exposing sensitive user data.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"private_messenger","vendor":"signal"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Signal Messenger for Android 4.24.8 may expose private information when using \"disappearing messages.\" If a user uses the photo feature available in the \"attach file\" menu, then Signal will leave the picture in its own cache directory, which is available to any application on the system.","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":"Information disclosure in Signal","id":"CVE-2018-3988","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-3989"},"packages":[],"prev":{"headline":"Information disclosure in Rakuten Viber","id":"CVE-2018-3987"},"products":["Signal"],"published":"2018-12-10","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2019-17192","kev_date_added":null,"published":"2019-10-05"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2019-17191","kev_date_added":null,"published":"2019-10-05"},{"cvss_score":6.5,"headline":"Other in n/a","id":"CVE-2019-9970","kev_date_added":null,"published":"2019-03-24"},{"cvss_score":5.3,"headline":"Information disclosure in Signal Private Messenger","id":"CVE-2020-5753","kev_date_added":null,"published":"2020-05-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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Signal for Android may leak private photos to other apps via cache when using disappearing messages, exposing sensitive user data.","url":"https://insights.sbomify.com/CVE-2018-3988/"}