{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1150 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1150 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1150 is a medium-severity vulnerability in n/a, published on 1 Oct 2002. 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-2002-1150 and fix it if it is affected.\n\nWhat it is: CVE-2002-1150 is a medium-severity vulnerability in n/a, published on 1 Oct 2002. 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-2002-1150 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-2002-1150/ (Markdown: https://insights.sbomify.com/CVE-2002-1150/index.md)","id":"CVE-2002-1150","markdown":"https://insights.sbomify.com/CVE-2002-1150/index.md","name":"CVE-2002-1150","record":{"aliases":["GHSA-w2f9-3chr-2j98"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"NetMeeting remote sharing","requires_auth":"none","summary":"Attackers with physical access can hijack remote sessions in Microsoft NetMeeting by bypassing screen saver protection via system shutdown sequences.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netmeeting","vendor":"microsoft"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"AV:L/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The Remote Desktop Sharing (RDS) Screen Saver Protection capability for Microsoft NetMeeting 3.01 through SP2 (4.4.3396) allows attackers with physical access to hijack remote sessions by entering certain logoff or shutdown sequences (such as CTRL-ALT-DEL) and canceling out of the resulting user confirmation prompts, such as when the remote user is editing a document.","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":"Security feature bypass in n/a","id":"CVE-2002-1150","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2002-1151"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2002-1149"},"products":["n/a"],"published":"2002-10-01","related":[{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2006-2919","kev_date_added":null,"published":"2006-06-09"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0533","kev_date_added":null,"published":"2004-04-16"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2003-0719","kev_date_added":null,"published":"2004-04-16"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2004-0117","kev_date_added":null,"published":"2004-04-16"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-1999-0332","kev_date_added":null,"published":"1999-09-29"},{"cvss_score":6.4,"headline":"Information disclosure in n/a","id":"CVE-1999-1097","kev_date_added":null,"published":"2001-09-12"},{"cvss_score":5,"headline":"Path traversal in n/a","id":"CVE-2003-0505","kev_date_added":null,"published":"2003-07-04"}],"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-08","vendors":["n/a"]},"summary":"Attackers with physical access can hijack remote sessions in Microsoft NetMeeting by bypassing screen saver protection via system shutdown sequences.","url":"https://insights.sbomify.com/CVE-2002-1150/"}