Skip to content
Fencer Intel
high 8.1

CVE-2018-1000130 in the critical feed json

Injection in Jolokia agent

published 8y ago modified 4mo ago also GHSA-rhqj-4pp8-vvgf , EUVD-2022-5177

cvss
8.1
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
73.7%
EPSS 73.7% chance of exploitation in 30 days, percentile 99.4%
public exploits
0
none known, plus a Nuclei check

Summary

A JNDI Injection vulnerability exists in Jolokia agent version 1.3.7 in the proxy mode that allows a remote attacker to run arbitrary Java code on the server.

Patch / fix

  • maven org.jolokia:jolokia-core 1.5.0

Is CVE-2018-1000130 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000130 updated cvss 8.1

jolokia: JMX proxy mode vulnerable to remote code execution

  • Red Hat AMQ Broker 7 jolokia-core jolokia-core
    affected: no fix available
  • Red Hat JBoss A-MQ 6 jolokia-core jolokia-core
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Data Virtualization 6 jolokia-client-java jolokia-client-java
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Fuse 6 jolokia-core jolokia-core
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse Integration Service 2 jolokia-core jolokia-core
    affected: no fix available
  • Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat OpenStack Platform 12 (Pike) opendaylight Red Hat OpenStack Platform 13 (Queens) opendaylight
    affected: no fix planned “Will not fix”
  • Red Hat Fuse 7
    fixed: vendor fix RHSA-2018:2669
  • Red Hat JBoss Developer Studio 11 jolokia-core jolokia-core Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) opendaylight Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 11 (Ocata) opendaylight
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

73.71% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P
GitHub 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
maven org.jolokia:jolokia-core
>=1.3.7, <1.5.0
1.5.0

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.