{"answers":{"affected":"2 open source packages ship an affected version, including com.gitblit:gitblit. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31267 in the wild and no public exploit code.","fix":"Upgrade com.gitblit:gitblit to 1.9.3 or later.","what":"CVE-2022-31267 is a critical vulnerability in n/a, published on 21 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31267 and fix it if it is affected.\n\nWhat it is: CVE-2022-31267 is a critical vulnerability in n/a, published on 21 May 2022. 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-2022-31267 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.gitblit:gitblit (Maven): affected all versions; fixed in 1.9.3\n- com.gitblit:gitblit (Maven): affected all versions; fixed in 1.9.3\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-2022-31267/ (Markdown: https://insights.sbomify.com/CVE-2022-31267/index.md)","id":"CVE-2022-31267","markdown":"https://insights.sbomify.com/CVE-2022-31267/index.md","name":"CVE-2022-31267","record":{"aliases":["GHSA-fh55-vwjc-69c7"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Gitblit Git server","requires_auth":"none","summary":"Attackers can escalate privileges to admin by injecting control characters into profile fields in Gitblit.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gitblit","vendor":"gitblit"}],"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-269","name":"Improper Privilege Management"}],"description":"Gitblit 1.9.2 allows privilege escalation via the Config User Service: a control character can be placed in a profile data field, such as an emailAddress%3Atext 'attacker@example.com\\n\\trole = \"#admin\"' value.","ecosystems":["Maven"],"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":"Unescaped control characters in Gitblit","id":"CVE-2022-31267","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Path traversal in Gitblit","id":"CVE-2022-31268"},"packages":[{"ecosystem":"Maven","fixed":["1.9.3"],"introduced":["0"],"last_affected":[],"package":"com.gitblit:gitblit","purl":null,"source":"GHSA-fh55-vwjc-69c7"},{"ecosystem":"Maven","fixed":["1.9.3"],"introduced":["0"],"last_affected":[],"package":"com.gitblit:gitblit","purl":"pkg:maven/com.gitblit/gitblit","source":"GHSA-fh55-vwjc-69c7"}],"prev":{"headline":"Business logic in n/a","id":"CVE-2022-31266"},"products":["n/a"],"published":"2022-05-21","related":[{"cvss_score":7.5,"headline":"Path traversal in Gitblit","id":"CVE-2022-31268","kev_date_added":null,"published":"2022-05-21"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-50977","kev_date_added":null,"published":"2025-08-27"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2025-50978","kev_date_added":null,"published":"2025-08-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["n/a"]},"summary":"Attackers can escalate privileges to admin by injecting control characters into profile fields in Gitblit.","url":"https://insights.sbomify.com/CVE-2022-31267/"}