{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:token-macro. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-1003011 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:token-macro to 2.6 or later.","what":"CVE-2019-1003011 is a high-severity denial of service vulnerability in Redhat Openshift Container Platform, published on 6 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-1003011 and fix it if it is affected.\n\nWhat it is: CVE-2019-1003011 is a high-severity denial of service vulnerability in Redhat Openshift Container Platform, published on 6 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-1003011 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:token-macro (Maven): affected all versions; fixed in 2.6\n- org.jenkins-ci.plugins:token-macro (Maven): affected all versions; fixed in 2.6\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-1003011/ (Markdown: https://insights.sbomify.com/CVE-2019-1003011/index.md)","id":"CVE-2019-1003011","markdown":"https://insights.sbomify.com/CVE-2019-1003011/index.md","name":"CVE-2019-1003011","record":{"aliases":["GHSA-23h9-m55m-c5jp"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins Token Macro Plugin","requires_auth":"low_privilege","summary":"Attackers controlling token macro input can trigger recursive evaluation, causing denial of service and information exposure in Jenkins.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jenkins","cpe":[{"product":"token_macro","vendor":"jenkins"},{"product":"openshift_container_platform","vendor":"redhat"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"An information exposure and denial of service vulnerability exists in Jenkins Token Macro Plugin 2.5 and earlier in src/main/java/org/jenkinsci/plugins/tokenmacro/Parser.java, src/main/java/org/jenkinsci/plugins/tokenmacro/TokenMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/AbstractChangesSinceMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ChangesSinceLastBuildMacro.java, src/main/java/org/jenkinsci/plugins/tokenmacro/impl/ProjectUrlMacro.java that allows attackers with the ability to control token macro input (such as SCM changelogs) to define recursive input that results in unexpected macro evaluation.","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 Token Macro Plugin's recursive token expansion results in information disclosure and DoS","id":"CVE-2019-1003011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"redhat:openshift_container_platform","products":["redhat:openshift_container_platform"],"type":"denial_of_service","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Cross-Site Request Forgery in Jenkins Blue Ocean Plugin","id":"CVE-2019-1003012"},"packages":[{"ecosystem":"Maven","fixed":["2.6"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:token-macro","purl":null,"source":"GHSA-23h9-m55m-c5jp"},{"ecosystem":"Maven","fixed":["2.6"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:token-macro","purl":"pkg:maven/org.jenkins-ci.plugins/token-macro","source":"GHSA-23h9-m55m-c5jp"}],"prev":{"headline":"Cross-Site Request Forgery in Jenkins Git Plugin","id":"CVE-2019-1003010"},"products":["Jenkins Token Macro Plugin"],"published":"2019-02-06","related":[{"cvss_score":7.5,"headline":"Improper Restriction of XML External Entity Reference Jenkins Token Macro Plugin","id":"CVE-2019-10337","kev_date_added":null,"published":"2019-06-11"}],"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 controlling token macro input can trigger recursive evaluation, causing denial of service and information exposure in Jenkins.","url":"https://insights.sbomify.com/CVE-2019-1003011/"}