{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-12613 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-12613 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-12613 is a high-severity vulnerability in n/a, published on 11 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12613 and fix it if it is affected.\n\nWhat it is: CVE-2020-12613 is a high-severity vulnerability in n/a, published on 11 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-12613 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-12613/ (Markdown: https://insights.sbomify.com/CVE-2020-12613/index.md)","id":"CVE-2020-12613","markdown":"https://insights.sbomify.com/CVE-2020-12613/index.md","name":"CVE-2020-12613","record":{"aliases":["GHSA-5jjx-mxcx-8c3v"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Privilege Management for Windows","requires_auth":"low_privilege","summary":"Attackers can retain unauthorized access via secondary user tokens during process elevation, enabling privilege escalation in BeyondTrust Privilege Management for Windows.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"privilege_management_for_windows","vendor":"beyondtrust"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in BeyondTrust Privilege Management for Windows through 5.6. An attacker can spawn a process with multiple users as part of the security token (prior to Avecto elevation). When Avecto elevates the process, it removes the user who is launching the process, but not the second user. Therefore this second user still retains access and can give permission to the process back to the first user.","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-12613","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-12614"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2020-12612"},"products":["n/a"],"published":"2023-12-11","related":[{"cvss_score":8.4,"headline":"Privilege escalation in n/a","id":"CVE-2020-12614","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-12612","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-12615","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2020-28369","kev_date_added":null,"published":"2023-12-12"},{"cvss_score":7.8,"headline":"Information disclosure in n/a","id":"CVE-2021-42254","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":7.2,"headline":"Privilege Management for Windows - Elevation of Privilege","id":"CVE-2025-2297","kev_date_added":null,"published":"2025-07-28"}],"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-04","vendors":["n/a"]},"summary":"Attackers can retain unauthorized access via secondary user tokens during process elevation, enabling privilege escalation in BeyondTrust Privilege Management for Windows.","url":"https://insights.sbomify.com/CVE-2020-12613/"}