{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15316 is a high-severity vulnerability in n/a, published on 21 Aug 2019. 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-2019-15316 and fix it if it is affected.\n\nWhat it is: CVE-2019-15316 is a high-severity vulnerability in n/a, published on 21 Aug 2019. 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-2019-15316 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-2019-15316/ (Markdown: https://insights.sbomify.com/CVE-2019-15316/index.md)","id":"CVE-2019-15316","markdown":"https://insights.sbomify.com/CVE-2019-15316/index.md","name":"CVE-2019-15316","record":{"aliases":["GHSA-x7v3-vhf3-7wrh"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Steam Client","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges to SYSTEM via a race condition in Steam Client for Windows due to weak folder permissions.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"steam_client","vendor":"valvesoftware"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"Valve Steam Client for Windows through 2019-08-20 has weak folder permissions, leading to privilege escalation (to NT AUTHORITY\\SYSTEM) via crafted use of CreateMountPoint.exe and SetOpLock.exe to leverage a TOCTOU race condition.","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":"Race condition in n/a","id":"CVE-2019-15316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2019"},"n_packages":0,"n_references":4,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-15317"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-15315"},"products":["n/a"],"published":"2019-08-21","related":[{"cvss_score":8,"headline":"Memory corruption in n/a","id":"CVE-2021-30481","kev_date_added":null,"published":"2021-04-10"},{"cvss_score":7.8,"headline":"Race condition in n/a","id":"CVE-2020-15530","kev_date_added":null,"published":"2020-07-05"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2019-17180","kev_date_added":null,"published":"2019-10-04"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-15315","kev_date_added":null,"published":"2019-08-21"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2015-7985","kev_date_added":null,"published":"2015-11-24"},{"cvss_score":6.6,"headline":"Privilege escalation in n/a","id":"CVE-2019-14743","kev_date_added":null,"published":"2019-08-07"}],"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-05","vendors":["n/a"]},"summary":"Local attackers can escalate privileges to SYSTEM via a race condition in Steam Client for Windows due to weak folder permissions.","url":"https://insights.sbomify.com/CVE-2019-15316/"}