{"answers":{"affected":"2 open source packages ship an affected version, including org.jvnet.hudson.plugins:analysis-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1000102 in the wild and no public exploit code.","fix":"Upgrade org.jvnet.hudson.plugins:analysis-core to 1.92 or later.","what":"CVE-2017-1000102 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Oct 2017. 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-2017-1000102 and fix it if it is affected.\n\nWhat it is: CVE-2017-1000102 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Oct 2017. 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-2017-1000102 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jvnet.hudson.plugins:analysis-core (Maven): affected all versions; fixed in 1.92\n- org.jvnet.hudson.plugins:analysis-core (Maven): affected all versions; fixed in 1.92\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-2017-1000102/ (Markdown: https://insights.sbomify.com/CVE-2017-1000102/index.md)","id":"CVE-2017-1000102","markdown":"https://insights.sbomify.com/CVE-2017-1000102/index.md","name":"CVE-2017-1000102","record":{"aliases":["GHSA-9c2p-99pg-c4j9"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Static Analysis Plugin","requires_auth":"low_privilege","summary":"Attackers can inject malicious HTML into the Details view of Static Analysis Utilities plugins via manipulated console output, potentially executing scripts in the user's browser.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"static_analysis_utilities","vendor":"jenkins"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Details view of some Static Analysis Utilities based plugins, was vulnerable to a persisted cross-site scripting vulnerability: Malicious users able to influence the input to these plugins, for example the console output which is parsed to extract build warnings (Warnings Plugin), could insert arbitrary HTML into this view.","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":"Persistent XSS vulnerability in Static Analysis Utilities","id":"CVE-2017-1000102","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2017"},"n_packages":2,"n_references":2,"next":{"headline":"Persistent XSS vulnerability in Jenkins DRY Plugin","id":"CVE-2017-1000103"},"packages":[{"ecosystem":"Maven","fixed":["1.92"],"introduced":["0"],"last_affected":[],"package":"org.jvnet.hudson.plugins:analysis-core","purl":null,"source":"GHSA-9c2p-99pg-c4j9"},{"ecosystem":"Maven","fixed":["1.92"],"introduced":["0"],"last_affected":[],"package":"org.jvnet.hudson.plugins:analysis-core","purl":"pkg:maven/org.jvnet.hudson.plugins/analysis-core","source":"GHSA-9c2p-99pg-c4j9"}],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-1000101"},"products":["n/a"],"published":"2017-10-04","related":[{"cvss_score":6.5,"headline":"Jenkins Static Analysis Utilities Plugin is vulnerable to Cross-site request forgery vulnerability","id":"CVE-2019-10307","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":6.5,"headline":"Missing permission check in Jenkins Static Analysis Utilities Plugin","id":"CVE-2019-10308","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":5.4,"headline":"Stored XSS vulnerability in Jenkins Static Analysis Utilities Plugin","id":"CVE-2020-2316","kev_date_added":null,"published":"2020-11-04"}],"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":["n/a"]},"summary":"Attackers can inject malicious HTML into the Details view of Static Analysis Utilities plugins via manipulated console output, potentially executing scripts in the user's browser.","url":"https://insights.sbomify.com/CVE-2017-1000102/"}