CVE-2018-12432: Cross-site Scripting in JavaMelody

Summary

14/05/2022
Yes i
Moderate
6.1

CVE-2018-12432: Cross-site Scripting in JavaMelody. Affects net.bull.javamelody:javamelody-core versions < 1.61.0. Fixed in 1.61.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

JavaMelody is a monitoring tool for Java applications that provides real-time information about the performance and health of the application. It is commonly used to monitor web applications, servlets, EJBs, and other Java components. The vulnerability identified as CVE-2018-12432 is a cross-site scripting (XSS) vulnerability that exists in JavaMelody versions up to 1.60.0. This vulnerability allows an attacker to inject malicious scripts into the application, potentially leading to unauthorized access, data theft, or other malicious activities.

Vulnerability Detail

The vulnerability arises due to insufficient input sanitization in the 'counter' parameter of the 'clear_counter' action in the '/monitoring' URI. An attacker can exploit this vulnerability by injecting malicious scripts into the 'counter' parameter, which will be executed when the action is triggered. This can be done by tricking a user with sufficient privileges to click on a specially crafted link or by manipulating the application's request parameters. The impact of this vulnerability can range from defacement of the application to the theft of sensitive user information.

How To Fix

Minimum fixed version

1.61.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version of JavaMelody is not immediately feasible, a temporary workaround can be implemented by manually sanitizing and validating the 'counter' parameter before using it in the application. This can be done by using a library or framework that provides input validation and sanitization functions, such as OWASP Java Encoder. By applying proper input sanitization, the risk of XSS attacks can be mitigated.

Conclusion

The CVE-2018-12432 vulnerability in JavaMelody exposes applications to cross-site scripting attacks. To mitigate this vulnerability, it is crucial to upgrade to JavaMelody version 1.61.0 or later. Alternatively, implementing proper input sanitization and validation for the 'counter' parameter can provide a temporary workaround. For further assistance or support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for net.bull.javamelody:javamelody-core →

Share this vulnerability

FAQ

The vulnerability allows an attacker to inject malicious scripts into the application, potentially leading to unauthorized access, data theft, or other malicious activities.

An attacker can exploit this vulnerability by injecting malicious scripts into the 'counter' parameter of the 'clear_counter' action in the '/monitoring' URI.

The recommended solution is to upgrade to JavaMelody version 1.61.0 or later, which includes a fix for the XSS vulnerability.

A temporary workaround is to manually sanitize and validate the 'counter' parameter before using it in the application.

There are no known public exploits for this vulnerability at the time of this report.

Related vulnerabilities

Recent vulnerabilities recorded for net.bull.javamelody:javamelody-core.

How To Fix

Minimum fixed version

1.61.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback