{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2007-4969 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2007-4969 yet. Limit exposure of the affected software until one is available.","what":"CVE-2007-4969 is a medium-severity vulnerability in n/a, published on 19 Sep 2007. 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-2007-4969 and fix it if it is affected.\n\nWhat it is: CVE-2007-4969 is a medium-severity vulnerability in n/a, published on 19 Sep 2007. 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-2007-4969 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-2007-4969/ (Markdown: https://insights.sbomify.com/CVE-2007-4969/index.md)","id":"CVE-2007-4969","markdown":"https://insights.sbomify.com/CVE-2007-4969/index.md","name":"CVE-2007-4969","record":{"aliases":["GHSA-4fv8-h7r9-m88g"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windows Process Monitor","requires_auth":"low_privilege","summary":"Local attackers can exploit improper SSDT validation in Process Monitor to crash the system or escalate privileges via kernel hooks.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"process_monitor","vendor":"sysinternals"}],"cvss":{"score":4.4,"severity":"medium","source":"nvd","vector":"AV:L/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Process Monitor 1.22 does not properly validate certain parameters to System Service Descriptor Table (SSDT) function handlers, which allows local users to cause a denial of service (crash) and possibly gain privileges via unspecified kernel SSDT hooks for Windows Native API functions including (1) NtCreateKey, (2) NtDeleteValueKey, (3) NtLoadKey, (4) NtOpenKey, (5) NtQueryValueKey, (6) NtSetValueKey, and (7) NtUnloadKey.","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":"Privilege escalation in n/a","id":"CVE-2007-4969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2007"},"n_packages":0,"n_references":5,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2007-4970"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2007-4968"},"products":["n/a"],"published":"2007-09-19","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":"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-07","vendors":["n/a"]},"summary":"Local attackers can exploit improper SSDT validation in Process Monitor to crash the system or escalate privileges via kernel hooks.","url":"https://insights.sbomify.com/CVE-2007-4969/"}