{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:gitlab-plugin. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-43411 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:gitlab-plugin to 1.5.36 or later.","what":"CVE-2022-43411 is a medium-severity vulnerability in Jenkins GitLab Plugin, published on 19 Oct 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-43411 and fix it if it is affected.\n\nWhat it is: CVE-2022-43411 is a medium-severity vulnerability in Jenkins GitLab Plugin, published on 19 Oct 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-43411 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:gitlab-plugin (Maven): affected all versions; fixed in 1.5.36\n- org.jenkins-ci.plugins:gitlab-plugin (Maven): affected all versions; fixed in 1.5.36\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-43411/ (Markdown: https://insights.sbomify.com/CVE-2022-43411/index.md)","id":"CVE-2022-43411","markdown":"https://insights.sbomify.com/CVE-2022-43411/index.md","name":"CVE-2022-43411","record":{"aliases":["GHSA-f9f9-4r63-4qcc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GitLab Plugin","requires_auth":"none","summary":"Attackers can statistically recover valid webhook tokens due to non-constant time comparison, bypassing authentication checks in the Jenkins GitLab Plugin.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gitlab","vendor":"jenkins"}],"cvss":{"score":5.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Jenkins GitLab Plugin 1.5.35 and earlier uses a non-constant time comparison function when checking whether the provided and expected webhook token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook token.","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":"Non-constant time webhook token comparison in Jenkins GitLab Plugin","id":"CVE-2022-43411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":2,"n_references":2,"next":{"headline":"Non-constant time webhook token comparison in Jenkins Generic Webhook Trigger Plugin","id":"CVE-2022-43412"},"packages":[{"ecosystem":"Maven","fixed":["1.5.36"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":null,"source":"GHSA-f9f9-4r63-4qcc"},{"ecosystem":"Maven","fixed":["1.5.36"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":"pkg:maven/org.jenkins-ci.plugins/gitlab-plugin","source":"GHSA-f9f9-4r63-4qcc"}],"prev":{"headline":"Webhook endpoint discloses job names to unauthorized users in Jenkins Mercurial Plugin","id":"CVE-2022-43410"},"products":["Jenkins GitLab Plugin"],"published":"2022-10-19","related":[{"cvss_score":8.8,"headline":"Jenkins GitLab Plugin missing permission checks","id":"CVE-2019-10301","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":8,"headline":"Jenkins GitLab Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2019-10300","kev_date_added":null,"published":"2019-04-18"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins GitLab Plugin","id":"CVE-2022-30955","kev_date_added":null,"published":"2022-05-17"},{"cvss_score":5.4,"headline":"Cross-site Scripting in Jenkins GitLab Plugin","id":"CVE-2022-34777","kev_date_added":null,"published":"2022-06-30"},{"cvss_score":4.3,"headline":"Incorrect permission check in Jenkins GitLab Plugin allows enumerating credentials IDs","id":"CVE-2025-24397","kev_date_added":null,"published":"2025-01-22"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-08","vendors":["Jenkins project"]},"summary":"Attackers can statistically recover valid webhook tokens due to non-constant time comparison, bypassing authentication checks in the Jenkins GitLab Plugin.","url":"https://insights.sbomify.com/CVE-2022-43411/"}