{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22861 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22861 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22861 is a medium-severity missing authorization vulnerability in GitHub Enterprise Server, published on 3 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-22861 and fix it if it is affected.\n\nWhat it is: CVE-2021-22861 is a medium-severity missing authorization vulnerability in GitHub Enterprise Server, published on 3 Mar 2021. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-22861 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-2021-22861/ (Markdown: https://insights.sbomify.com/CVE-2021-22861/index.md)","id":"CVE-2021-22861","markdown":"https://insights.sbomify.com/CVE-2021-22861/index.md","name":"CVE-2021-22861","record":{"aliases":["GHSA-x87g-4c45-mvv5"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"GitHub Enterprise Server","requires_auth":"low_privilege","summary":"Authenticated users can gain unauthorized write access to forkable repositories via crafted pull requests and API calls.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_P","cpe":[{"product":"github","vendor":"github"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"}],"description":"An improper access control vulnerability was identified in GitHub Enterprise Server that allowed authenticated users of the instance to gain write access to unauthorized repositories via specifically crafted pull requests and REST API requests. An attacker would need to be able to fork the targeted repository, a setting that is disabled by default for organization owned private repositories. Branch protections such as required pull request reviews or status checks would prevent unauthorized commits from being merged without further review or validation. This vulnerability affected all versions of GitHub Enterprise Server since 2.4.21 and was fixed in versions 2.20.24, 2.21.15, 2.22.7 and 3.0.1. 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 unauthorized write access to forkable repositories","id":"CVE-2021-22861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":4,"next":{"headline":"Improper access control in GitHub Enterprise Server leading to the disclosure of Actions secrets to forks","id":"CVE-2021-22862"},"packages":[],"prev":{"headline":"EIC e-document system - Broken Authentication","id":"CVE-2021-22860"},"products":["GitHub Enterprise Server"],"published":"2021-03-03","related":[{"cvss_score":9.8,"headline":"Improper access control in GitHub Enterprise Server leading to privilege escalation of organization member","id":"CVE-2020-10516","kev_date_added":null,"published":"2020-06-03"},{"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"}],"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-03","vendors":["GitHub"]},"summary":"Authenticated users can gain unauthorized write access to forkable repositories via crafted pull requests and API calls.","url":"https://insights.sbomify.com/CVE-2021-22861/"}