{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-8239 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-8239 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-8239 is a critical vulnerability in Pulse Secure Desktop Cient, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-8239 and fix it if it is affected.\n\nWhat it is: CVE-2020-8239 is a critical vulnerability in Pulse Secure Desktop Cient, published on 28 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-8239 in the wild and no public exploit code.\n\nAffected product: Pulse Secure Desktop Cient. 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-8239/ (Markdown: https://insights.sbomify.com/CVE-2020-8239/index.md)","id":"CVE-2020-8239","markdown":"https://insights.sbomify.com/CVE-2020-8239/index.md","name":"CVE-2020-8239","record":{"aliases":["GHSA-x363-jjj2-3345"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Pulse Secure Desktop Client","requires_auth":"none","summary":"Attackers can escalate privileges via a client registry vulnerability in the Pulse Secure Desktop Client, requiring both client and server upgrades.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"pulse_secure_desktop_client","vendor":"pulsesecure"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"A vulnerability in the Pulse Secure Desktop Client \u003c 9.1R9 is vulnerable to the client registry privilege escalation attack. This fix also requires Server Side Upgrade due to Standalone Host Checker Client (Windows) and Windows PDC.","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 Pulse Secure Desktop Cient","id":"CVE-2020-8239","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":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8240"},"packages":[],"prev":{"headline":"Cross-site scripting in Pulse Connect Secure/ Pulse Policy Secure","id":"CVE-2020-8238"},"products":["Pulse Secure Desktop Cient"],"published":"2020-10-28","related":[{"cvss_score":8.8,"headline":"Path traversal in Pulse Secure Desktop Client","id":"CVE-2020-8254","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8240","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8248","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Memory corruption in Pulse Secure Desktop Client","id":"CVE-2020-8249","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in Pulse Secure Desktop Client","id":"CVE-2020-8250","kev_date_added":null,"published":"2020-10-28"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-15865","kev_date_added":null,"published":"2018-09-06"}],"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 escalate privileges via a client registry vulnerability in the Pulse Secure Desktop Client, requiring both client and server upgrades.","url":"https://insights.sbomify.com/CVE-2020-8239/"}