{"answers":{"affected":"2 open source packages ship an affected version, including net.bull.javamelody:javamelody-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12432 in the wild and no public exploit code.","fix":"Upgrade net.bull.javamelody:javamelody-core to 1.61.0 or later.","what":"CVE-2018-12432 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-12432 and fix it if it is affected.\n\nWhat it is: CVE-2018-12432 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-12432 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- net.bull.javamelody:javamelody-core (Maven): affected all versions; fixed in 1.61.0\n- net.bull.javamelody:javamelody-core (Maven): affected all versions; fixed in 1.61.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-12432/ (Markdown: https://insights.sbomify.com/CVE-2018-12432/index.md)","id":"CVE-2018-12432","markdown":"https://insights.sbomify.com/CVE-2018-12432/index.md","name":"CVE-2018-12432","record":{"aliases":["GHSA-g66q-grxc-64j3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Java monitoring library","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via the counter parameter in JavaMelody monitoring actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"javamelody","vendor":"javamelody_project"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/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":"JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.","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":"Cross-site Scripting in JavaMelody","id":"CVE-2018-12432","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2018"},"n_packages":2,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-12433"},"packages":[{"ecosystem":"Maven","fixed":["1.61.0"],"introduced":["0"],"last_affected":[],"package":"net.bull.javamelody:javamelody-core","purl":null,"source":"GHSA-g66q-grxc-64j3"},{"ecosystem":"Maven","fixed":["1.61.0"],"introduced":["0"],"last_affected":[],"package":"net.bull.javamelody:javamelody-core","purl":"pkg:maven/net.bull.javamelody/javamelody-core","source":"GHSA-g66q-grxc-64j3"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-12431"},"products":["n/a"],"published":"2018-06-14","related":[{"cvss_score":9.8,"headline":"JavaMelody has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.","id":"CVE-2018-15531","kev_date_added":null,"published":"2018-09-26"}],"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 execute arbitrary scripts in victim browsers via the counter parameter in JavaMelody monitoring actions.","url":"https://insights.sbomify.com/CVE-2018-12432/"}