{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10516 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10516 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10516 is a critical vulnerability in GitHub Enterprise Server, published on 3 Jun 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-10516 and fix it if it is affected.\n\nWhat it is: CVE-2020-10516 is a critical vulnerability in GitHub Enterprise Server, published on 3 Jun 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-10516 in the wild and no public exploit code.\n\nAffected product: GitHub Enterprise Server. 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-10516/ (Markdown: https://insights.sbomify.com/CVE-2020-10516/index.md)","id":"CVE-2020-10516","markdown":"https://insights.sbomify.com/CVE-2020-10516/index.md","name":"CVE-2020-10516","record":{"aliases":["GHSA-f436-2f67-fg74"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Enterprise Server","requires_auth":"none","summary":"An organization member can escalate permissions to access unauthorized repositories within the organization via the API.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_P","cpe":[{"product":"github","vendor":"github"}],"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":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"An improper access control vulnerability was identified in the GitHub Enterprise Server API that allowed an organization member to escalate permissions and gain access to unauthorized repositories within an organization. This vulnerability affected all versions of GitHub Enterprise Server prior to 2.21 and was fixed in 2.20.9, 2.19.15, and 2.18.20. This vulnerability was reported via the GitHub Bug Bounty program.","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":"Improper access control in GitHub Enterprise Server leading to privilege escalation of organization member","id":"CVE-2020-10516","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Improper access control in GitHub Enterprise Server leading to the enumeration of private repository names","id":"CVE-2020-10517"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2020-10515"},"products":["GitHub Enterprise Server"],"published":"2020-06-03","related":[{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2017-18365","kev_date_added":null,"published":"2019-03-28"},{"cvss_score":8.8,"headline":"Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server","id":"CVE-2020-10519","kev_date_added":null,"published":"2021-03-03"},{"cvss_score":8.8,"headline":"Unsafe configuration options in GitHub Pages leading to remote code execution on GitHub Enterprise Server","id":"CVE-2020-10518","kev_date_added":null,"published":"2020-08-27"},{"cvss_score":8.1,"headline":"Missing authorization in GitHub Enterprise Server","id":"CVE-2021-22863","kev_date_added":null,"published":"2021-03-03"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2012-2055","kev_date_added":null,"published":"2012-04-04"},{"cvss_score":6.5,"headline":"Improper access control in GitHub Enterprise Server leading to unauthorized write access to forkable repositories","id":"CVE-2021-22861","kev_date_added":null,"published":"2021-03-03"}],"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":["GitHub"]},"summary":"An organization member can escalate permissions to access unauthorized repositories within the organization via the API.","url":"https://insights.sbomify.com/CVE-2020-10516/"}