{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-3669 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-3669 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-3669 is a low-severity vulnerability in n/a, published on 17 Jul 2006. 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-2006-3669 and fix it if it is affected.\n\nWhat it is: CVE-2006-3669 is a low-severity vulnerability in n/a, published on 17 Jul 2006. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-3669 in the wild and no public exploit code.\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-2006-3669/ (Markdown: https://insights.sbomify.com/CVE-2006-3669/index.md)","id":"CVE-2006-3669","markdown":"https://insights.sbomify.com/CVE-2006-3669/index.md","name":"CVE-2006-3669","record":{"aliases":["GHSA-c48g-4mfx-p8f8"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Mac OS X messenger","requires_auth":"low_privilege","summary":"Local users can read other users' chat logs due to world-readable file permissions in Mercury Messenger on Mac OS X.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mercury_messenger","vendor":"mercury_messenger"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[],"description":"Mercury Messenger, possibly 1.7.1.1 and other versions, when running on a multi-user Mac OS X platform, stores chat logs with world-readable permissions within the /Users directory, which allows local users to read the chat logs from other users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2006-3669","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-3670"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2006-3668"},"products":["n/a"],"published":"2006-07-17","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Local users can read other users' chat logs due to world-readable file permissions in Mercury Messenger on Mac OS X.","url":"https://insights.sbomify.com/CVE-2006-3669/"}