CVE-2018-1000130: Injection in Jolokia agent

org.jolokia:jolokia-core Updated 02 Oct 2025

Summary

14/05/2022

Disclosed on

CVE-2018-1000130

CVE

Yes i

Fix available

High

Severity

8.1

CVSS Score

CVE-2018-1000130: Injection in Jolokia agent. Affects org.jolokia:jolokia-core versions >= 1.3.7, < 1.5.0. Fixed in 1.5.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 Browse

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.

Background

The Jolokia agent is a Java-based library that provides remote JMX access over HTTP. It is commonly used for monitoring and managing Java applications. The agent operates in proxy mode, allowing remote access to JMX MBeans on the server. This vulnerability affects Jolokia agent version 1.3.7 in proxy mode.

Vulnerability Detail

A JNDI Injection vulnerability exists in Jolokia agent version 1.3.7 in proxy mode. This vulnerability allows a remote attacker to inject arbitrary Java code into the server, potentially leading to remote code execution. By exploiting this vulnerability, an attacker can gain unauthorized access to the server and perform malicious actions.

How To Fix

Minimum fixed version

1.5.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 is not immediately feasible, a temporary workaround is to disable the Jolokia agent or restrict access to it. This can be done by removing or disabling the Jolokia agent from the application's configuration. However, this workaround may impact the functionality of monitoring and managing Java applications.

Conclusion

The Jolokia agent version 1.3.7 in proxy mode is vulnerable to a JNDI Injection vulnerability. It is recommended to upgrade to version 1.5.0 or later to fix this vulnerability. If immediate upgrade is not possible, consider applying the workaround of disabling or restricting access to the Jolokia agent. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for org.jolokia:jolokia-core →