{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:jms-messaging. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-1003028 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:jms-messaging to 1.1.2 or later.","what":"CVE-2019-1003028 is a medium-severity server-side request forgery vulnerability in Jenkins JMS Messaging Plugin, published on 20 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-1003028 and fix it if it is affected.\n\nWhat it is: CVE-2019-1003028 is a medium-severity server-side request forgery vulnerability in Jenkins JMS Messaging Plugin, published on 20 Feb 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-1003028 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:jms-messaging (Maven): affected all versions; fixed in 1.1.2\n- org.jenkins-ci.plugins:jms-messaging (Maven): affected all versions; fixed in 1.1.2\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-1003028/ (Markdown: https://insights.sbomify.com/CVE-2019-1003028/index.md)","id":"CVE-2019-1003028","markdown":"https://insights.sbomify.com/CVE-2019-1003028/index.md","name":"CVE-2019-1003028","record":{"aliases":["GHSA-g3gj-632x-fhrh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins JMS Messaging Plugin","requires_auth":"low_privilege","summary":"Attackers with Read permission can force Jenkins to connect to arbitrary JMS endpoints, enabling server-side request forgery attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"jms_messaging","vendor":"jenkins"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"A server-side request forgery vulnerability exists in Jenkins JMS Messaging Plugin 1.1.1 and earlier in SSLCertificateAuthenticationMethod.java, UsernameAuthenticationMethod.java that allows attackers with Overall/Read permission to have Jenkins connect to a JMS endpoint.","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":"SSRF vulnerability due to missing permission check in Jenkins JMS Messaging Plugin","id":"CVE-2019-1003028","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"ssrf","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Jenkins Script Security Plugin Sandbox Bypass","id":"CVE-2019-1003029"},"packages":[{"ecosystem":"Maven","fixed":["1.1.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jms-messaging","purl":null,"source":"GHSA-g3gj-632x-fhrh"},{"ecosystem":"Maven","fixed":["1.1.2"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:jms-messaging","purl":"pkg:maven/org.jenkins-ci.plugins/jms-messaging","source":"GHSA-g3gj-632x-fhrh"}],"prev":{"headline":"SSRF vulnerability due to missing permission check in Jenkins OctopusDeploy Plugin","id":"CVE-2019-1003027"},"products":["Jenkins JMS Messaging Plugin"],"published":"2019-02-20","related":[],"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-05","vendors":["Jenkins project"]},"summary":"Attackers with Read permission can force Jenkins to connect to arbitrary JMS endpoints, enabling server-side request forgery attacks.","url":"https://insights.sbomify.com/CVE-2019-1003028/"}