{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-0363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-0363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-0363 is a low-severity vulnerability in n/a, published on 22 Jan 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-0363 and fix it if it is affected.\n\nWhat it is: CVE-2006-0363 is a low-severity vulnerability in n/a, published on 22 Jan 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-0363 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-0363/ (Markdown: https://insights.sbomify.com/CVE-2006-0363/index.md)","id":"CVE-2006-0363","markdown":"https://insights.sbomify.com/CVE-2006-0363/index.md","name":"CVE-2006-0363","record":{"aliases":["GHSA-7x7q-g489-cq27"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MSN Messenger","requires_auth":"none","summary":"Local attackers can recover stored MSN Messenger passwords by accessing registry keys and using standard decryption APIs.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"msn_messenger","vendor":"microsoft"}],"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":"The \"Remember my Password\" feature in MSN Messenger 7.5 stores passwords in an encrypted format under the HKEY_CURRENT_USER\\Software\\Microsoft\\IdentityCRL\\Creds registry key, which might allow local users to obtain the original passwords via a program that calls CryptUnprotectData, as demonstrated by the \"MSN Password Recovery.exe\" program.  NOTE: it could be argued that local-only password recovery is inherently insecure because the decryption methods and keys must be stored somewhere on the local system, and are thus inherently accessible with varying degrees of effort.  Perhaps this issue should not be included in CVE.","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-0363","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":"Cross-site scripting in n/a","id":"CVE-2006-0364"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2006-0362"},"products":["n/a"],"published":"2006-01-22","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2007-2931","kev_date_added":null,"published":"2007-08-31"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2005-0562","kev_date_added":null,"published":"2005-04-13"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2007-3436","kev_date_added":null,"published":"2007-06-27"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2002-1831","kev_date_added":null,"published":"2005-06-28"},{"cvss_score":5,"headline":"Memory corruption in n/a","id":"CVE-2002-1698","kev_date_added":null,"published":"2005-06-21"},{"cvss_score":5,"headline":"Information disclosure in n/a","id":"CVE-2004-0122","kev_date_added":null,"published":"2004-09-01"},{"cvss_score":5,"headline":"Auth bypass in n/a","id":"CVE-2002-0472","kev_date_added":null,"published":"2002-06-11"}],"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 attackers can recover stored MSN Messenger passwords by accessing registry keys and using standard decryption APIs.","url":"https://insights.sbomify.com/CVE-2006-0363/"}