{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-4149 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-4149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-4149 is a high-severity vulnerability in Netskope Client, published on 15 Jun 2023. 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-2022-4149 and fix it if it is affected.\n\nWhat it is: CVE-2022-4149 is a high-severity vulnerability in Netskope Client, published on 15 Jun 2023. 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-2022-4149 in the wild and no public exploit code.\n\nAffected product: Netskope Client. 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-2022-4149/ (Markdown: https://insights.sbomify.com/CVE-2022-4149/index.md)","id":"CVE-2022-4149","markdown":"https://insights.sbomify.com/CVE-2022-4149/index.md","name":"CVE-2022-4149","record":{"aliases":["GHSA-hrcj-xqpr-q9q7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Netskope Client","requires_auth":"low_privilege","summary":"A local attacker can exploit a race condition in the Netskope Client log file handling to escalate privileges to SYSTEM.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Netskope","cpe":[{"product":"netskope","vendor":"netskope"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"The Netskope client service (prior to R96) on Windows runs as NT AUTHORITY\\SYSTEM which writes log files to a writable directory (C:\\Users\\Public\\netSkope) for a standard user. The files are created and written with a SYSTEM account except one file (logplaceholder) which inherits permission giving all users full access control list. Netskope client restricts access to this file by allowing only read permissions as a standard user. Whenever the Netskope client service restarts, it deletes the logplaceholder and recreates, creating a race condition, which can be exploited by a malicious local user to create the file and set ACL permissions on the file. Once the file is created by a malicious user with proper ACL permissions, all files within C:\\Users\\Public\\netSkope\\ becomes modifiable by the unprivileged user. By using Windows pseudo-symlink, these files can be pointed to other places in the system and thus malicious users will be able to elevate privileges.","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":"Local privilege escalation using log file","id":"CVE-2022-4149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Contest Gallery \u003c 19.1.5 - Author+ SQL Injection","id":"CVE-2022-4150"},"packages":[],"prev":{"headline":"WP OAuth Server \u003c 4.3.0 - Subscriber+ Arbitrary Client Deletion","id":"CVE-2022-4148"},"products":["Netskope Client"],"published":"2023-06-15","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-24576","kev_date_added":null,"published":"2021-08-12"},{"cvss_score":8.5,"headline":"Client Enrollment Process Bypass","id":"CVE-2024-7401","kev_date_added":null,"published":"2024-08-26"},{"cvss_score":8.4,"headline":"Sensitive Information store in NSClient logs","id":"CVE-2021-44862","kev_date_added":null,"published":"2022-11-03"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-41388","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2020-28845","kev_date_added":null,"published":"2020-11-20"},{"cvss_score":7.8,"headline":"Netskope client command injections vulnerability","id":"CVE-2019-12091","kev_date_added":null,"published":"2019-09-26"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-12-12","vendors":["Netskope"]},"summary":"A local attacker can exploit a race condition in the Netskope Client log file handling to escalate privileges to SYSTEM.","url":"https://insights.sbomify.com/CVE-2022-4149/"}