PatchTheCVEjavamelody project vulnerabilities
Recent CVEs affecting javamelody project products. 2 tracked.
javamelody project has 2 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 2. Most recent: 2018-09-26. Highest priority: CVE-2018-15531 (score 64/100).
- CVE-2018-15531 CRITICAL 9.8 UPGRADE JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java.
- CVE-2018-12432 MEDIUM 6.1 UPGRADE JavaMelody through 1.60.0 has XSS via the counter parameter in a clear_counter action to the /monitoring URI.
FAQ
How do I fix javamelody project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is javamelody project being exploited right now?
None of the tracked javamelody project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which javamelody project CVE should I patch first?
CVE-2018-15531 currently ranks highest (64/100): JavaMelody before 1.74.0 has XXE via parseSoapMethodName in bull/javamelody/PayloadNameRequestWrapper.java..