{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39233 exists.","fix":"No fix has been published for CVE-2022-39233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39233 is a medium-severity missing authorization vulnerability in Enalean Tuleap, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-39233 and fix it if it is affected.\n\nWhat it is: CVE-2022-39233 is a medium-severity missing authorization vulnerability in Enalean Tuleap, published on 19 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39233 exists.\n\nAffected product: Enalean Tuleap. 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-2022-39233/ (Markdown: https://insights.sbomify.com/CVE-2022-39233/index.md)","id":"CVE-2022-39233","markdown":"https://insights.sbomify.com/CVE-2022-39233/index.md","name":"CVE-2022-39233","record":{"aliases":["GHSA-3884-972x-3ccq"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Tuleap collaboration suite","requires_auth":"low_privilege","summary":"Authenticated users can modify GitLab repository branch prefixes via a REST endpoint, bypassing restrictions intended for Git administrators.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tuleap","vendor":"enalean"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Tuleap is a Free \u0026 Open Source Suite to improve management of software developments and collaboration. In versions 12.9.99.228 and above, prior to 14.0.99.24, authorizations are not properly verified when updating the branch prefix used by the GitLab repository integration. Authenticated users can change the branch prefix of any of the GitLab repository integration they can see vie the REST endpoint `PATCH /gitlab_repositories/{id}`. This action should be restricted to Git administrators. This issue is patched in Tuleap Community Edition 14.0.99.24 and Tuleap Enterprise Edition 14.0-3. There are no known workarounds.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Tuleap subject to Missing Authorization allowing for branch prefix modification","id":"CVE-2022-39233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"enalean:tuleap","products":["enalean:tuleap"],"type":"missing_authorization","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"user session persists even after permanently deleting account in GLPI","id":"CVE-2022-39234"},"packages":[],"prev":{"headline":"Discourse vulnerable to incomplete quote causing a topic to crash in the browser","id":"CVE-2022-39232"},"products":["tuleap"],"published":"2022-10-19","related":[{"cvss_score":9.8,"headline":"Business logic in n/a","id":"CVE-2018-17298","kev_date_added":null,"published":"2018-09-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2018-7538","kev_date_added":null,"published":"2018-03-12"},{"cvss_score":9.3,"headline":"Command injection in n/a","id":"CVE-2014-7178","kev_date_added":null,"published":"2014-11-28"},{"cvss_score":8.8,"headline":"SQL injection in Tuleap","id":"CVE-2021-43806","kev_date_added":null,"published":"2021-12-15"},{"cvss_score":8.8,"headline":"SQL injection in the \"SVN core\" commits browser","id":"CVE-2021-41154","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"SQL injection in CVS revisions browser","id":"CVE-2021-41155","kev_date_added":null,"published":"2021-10-18"},{"cvss_score":8.8,"headline":"The update of the CI job targeted by a widget is vulnerable to blind SQL injections","id":"CVE-2021-41148","kev_date_added":null,"published":"2021-10-15"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["Enalean"]},"summary":"Authenticated users can modify GitLab repository branch prefixes via a REST endpoint, bypassing restrictions intended for Git administrators.","url":"https://insights.sbomify.com/CVE-2022-39233/"}