{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15529 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15529 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15529 is a high-severity vulnerability in n/a, published on 5 Jul 2020. 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-2020-15529 and fix it if it is affected.\n\nWhat it is: CVE-2020-15529 is a high-severity vulnerability in n/a, published on 5 Jul 2020. 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-2020-15529 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-2020-15529/ (Markdown: https://insights.sbomify.com/CVE-2020-15529/index.md)","id":"CVE-2020-15529","markdown":"https://insights.sbomify.com/CVE-2020-15529/index.md","name":"CVE-2020-15529","record":{"aliases":["GHSA-cj35-hhr2-7qgh"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GOG Galaxy Client","requires_auth":"none","summary":"Local attackers can escalate privileges via weak file permissions and opportunistic locks during game installation or repair in GOG Galaxy Client.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"galaxy","vendor":"gog"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-667","name":"Improper Locking"}],"description":"An issue was discovered in GOG Galaxy Client 2.0.17. Local escalation of privileges is possible when a user installs a game or performs a verify/repair operation. The issue exists because of weak file permissions and can be exploited by using opportunistic locks.","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-2020-15529","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in n/a","id":"CVE-2020-15530"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-15528"},"products":["n/a"],"published":"2020-07-05","related":[{"cvss_score":9.3,"headline":"Privilege escalation in GOG Galaxy","id":"CVE-2018-4048","kev_date_added":null,"published":"2019-05-30"},{"cvss_score":9.3,"headline":"Privilege escalation in GOG Galaxy","id":"CVE-2018-3974","kev_date_added":null,"published":"2019-04-02"},{"cvss_score":9.3,"headline":"Privilege escalation in GOG Galaxy","id":"CVE-2018-4049","kev_date_added":null,"published":"2019-04-02"},{"cvss_score":8.4,"headline":"GOG Galaxy GalaxyClientService Privilege Escalation","id":"CVE-2020-7352","kev_date_added":null,"published":"2020-08-06"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-31262","kev_date_added":null,"published":"2022-08-17"},{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2021-26807","kev_date_added":null,"published":"2021-04-30"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-24574","kev_date_added":null,"published":"2020-08-21"}],"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-04","vendors":["n/a"]},"summary":"Local attackers can escalate privileges via weak file permissions and opportunistic locks during game installation or repair in GOG Galaxy Client.","url":"https://insights.sbomify.com/CVE-2020-15529/"}