{"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-2019-10300 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:gitlab-plugin to 1.5.12 or later.","what":"CVE-2019-10300 is a high-severity vulnerability in Jenkins GitLab Plugin, published on 18 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-10300 and fix it if it is affected.\n\nWhat it is: CVE-2019-10300 is a high-severity vulnerability in Jenkins GitLab Plugin, published on 18 Apr 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-10300 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.12\n- org.jenkins-ci.plugins:gitlab-plugin (Maven): affected all versions; fixed in 1.5.12\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-2019-10300/ (Markdown: https://insights.sbomify.com/CVE-2019-10300/index.md)","id":"CVE-2019-10300","markdown":"https://insights.sbomify.com/CVE-2019-10300/index.md","name":"CVE-2019-10300","record":{"aliases":["GHSA-j365-62px-vjjv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins GitLab Plugin","requires_auth":"low_privilege","summary":"Attackers can exploit CSRF to connect Jenkins to malicious URLs, potentially capturing stored credentials via the GitLab plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"gitlab","vendor":"jenkins"}],"cvss":{"score":8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"A cross-site request forgery vulnerability in Jenkins GitLab Plugin 1.5.11 and earlier in the GitLabConnectionConfig#doTestConnection form validation method allowed attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.","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":"Jenkins GitLab Plugin Cross-Site Request Forgery vulnerability","id":"CVE-2019-10300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Jenkins GitLab Plugin missing permission checks","id":"CVE-2019-10301"},"packages":[{"ecosystem":"Maven","fixed":["1.5.12"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":null,"source":"GHSA-j365-62px-vjjv"},{"ecosystem":"Maven","fixed":["1.5.12"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:gitlab-plugin","purl":"pkg:maven/org.jenkins-ci.plugins/gitlab-plugin","source":"GHSA-j365-62px-vjjv"}],"prev":{"headline":"Jenkins CloudCoreo DeployTime Plugin stores credentials in plain text","id":"CVE-2019-10299"},"products":["Jenkins GitLab Plugin"],"published":"2019-04-18","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":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":5.3,"headline":"Non-constant time webhook token comparison in Jenkins GitLab Plugin","id":"CVE-2022-43411","kev_date_added":null,"published":"2022-10-19"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["Jenkins project"]},"summary":"Attackers can exploit CSRF to connect Jenkins to malicious URLs, potentially capturing stored credentials via the GitLab plugin.","url":"https://insights.sbomify.com/CVE-2019-10300/"}