{"answers":{"affected":"2 open source packages ship an affected version, including org.jenkins-ci.plugins:s3. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000177 in the wild and no public exploit code.","fix":"Upgrade org.jenkins-ci.plugins:s3 to 0.11.0 or later.","what":"CVE-2018-1000177 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2018. 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-2018-1000177 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000177 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 2018. 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-2018-1000177 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.0\n- org.jenkins-ci.plugins:s3 (Maven): affected all versions; fixed in 0.11.0\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-2018-1000177/ (Markdown: https://insights.sbomify.com/CVE-2018-1000177/index.md)","id":"CVE-2018-1000177","markdown":"https://insights.sbomify.com/CVE-2018-1000177/index.md","name":"CVE-2018-1000177","record":{"aliases":["GHSA-3892-qqv6-h2qm"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Jenkins S3 Plugin","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in other users' browsers via malicious file names in the Jenkins S3 Plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"s3_publisher","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":"A cross-site scripting vulnerability exists in Jenkins S3 Plugin 0.10.12 and older in src/main/resources/hudson/plugins/s3/S3ArtifactsProjectAction/jobMain.jelly that allows attackers able to control file names of uploaded files to define file names containing JavaScript that would be executed in another user's browser when that user performs some UI actions.","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":"Stored XSS vulnerability in Jenkins S3 Publisher Plugin","id":"CVE-2018-1000177","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-1000178"},"packages":[{"ecosystem":"Maven","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":null,"source":"GHSA-3892-qqv6-h2qm"},{"ecosystem":"Maven","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"org.jenkins-ci.plugins:s3","purl":"pkg:maven/org.jenkins-ci.plugins/s3","source":"GHSA-3892-qqv6-h2qm"}],"prev":{"headline":"Jenkins Email Extension Plugin showed plain text SMTP password in configuration form field","id":"CVE-2018-1000176"},"products":["n/a"],"published":"2018-05-08","related":[{"cvss_score":7.5,"headline":"Jenkins S3 Publisher Plugin transmits credentials in plain text during configuration","id":"CVE-2020-2114","kev_date_added":null,"published":"2020-02-12"},{"cvss_score":4.3,"headline":"Missing Authorization in Jenkins S3 publisher Plugin","id":"CVE-2021-21650","kev_date_added":null,"published":"2021-05-11"},{"cvss_score":4.3,"headline":"Missing Authorization in Jenkins S3 publisher Plugin","id":"CVE-2021-21651","kev_date_added":null,"published":"2021-05-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-09-17","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript in other users' browsers via malicious file names in the Jenkins S3 Plugin.","url":"https://insights.sbomify.com/CVE-2018-1000177/"}