{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16976 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-16976 is a high-severity vulnerability in n/a, published on 12 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16976 and fix it if it is affected.\n\nWhat it is: CVE-2018-16976 is a high-severity vulnerability in n/a, published on 12 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16976 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-2018-16976/ (Markdown: https://insights.sbomify.com/CVE-2018-16976/index.md)","id":"CVE-2018-16976","markdown":"https://insights.sbomify.com/CVE-2018-16976/index.md","name":"CVE-2018-16976","record":{"aliases":["DEBIAN-CVE-2018-16976","GHSA-jq3h-g8hj-7pmh","MGASA-2018-0434","UBUNTU-CVE-2018-16976"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Git repository management","requires_auth":"low_privilege","summary":"Attackers can bypass access controls during Git repository migration in specific configurations, gaining unintended access to repositories.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gitolite","vendor":"gitolite"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Gitolite before 3.6.9 does not (in certain configurations involving @all or a regex) properly restrict access to a Git repository that is in the process of being migrated until the full set of migration steps has been completed. This can allow valid users to obtain unintended access.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Race condition in n/a","id":"CVE-2018-16976","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-16977"},"packages":[],"prev":{"headline":"Elefant CMS PHP Code Execution Vulnerability","id":"CVE-2018-16975"},"products":["n/a"],"published":"2018-09-12","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2010-2447","kev_date_added":null,"published":"2019-11-07"},{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2013-4451","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2018-20683","kev_date_added":null,"published":"2019-01-10"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2011-1572","kev_date_added":null,"published":"2011-10-04"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2013-7203","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":4.6,"headline":"Path traversal in n/a","id":"CVE-2012-4506","kev_date_added":null,"published":"2012-10-22"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can bypass access controls during Git repository migration in specific configurations, gaining unintended access to repositories.","url":"https://insights.sbomify.com/CVE-2018-16976/"}