Skip to content
Fencer Intel
high 8.1

CVE-2018-10899 json

Cross-Site Request Forgery in Jolokia

published 7y ago modified 4mo ago also GHSA-xcxf-7q4p-cj26 , EUVD-2022-5769

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

A flaw was found in Jolokia versions from 1.2 to before 1.6.1. Affected versions are vulnerable to a system-wide CSRF. This holds true for properly configured instances with strict checking for origin and referrer headers. This could result in a Remote Code Execution attack.

Patch / fix

  • maven org.jolokia:jolokia-core 1.6.1
  • jolokia jolokia 1.6.1

Is CVE-2018-10899 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-10899 updated cvss 8.1

jolokia: system-wide CSRF that could lead to Remote Code Execution

  • Red Hat JBoss Developer Studio 11 jolokia-core jolokia-core
    affected: no fix planned “Out of support scope”
  • Red Hat AMQ Broker 7 jolokia-core jolokia-core
    affected: no fix available
  • Red Hat Enterprise Linux OpenStack Platform 7 (Kilo) opendaylight Red Hat OpenStack Platform 8 (Liberty) opendaylight Red Hat OpenStack Platform 9 (Mitaka) opendaylight Red Hat OpenStack Platform 10 (Newton) opendaylight Red Hat OpenStack Platform 12 (Pike) opendaylight
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) opendaylight
    affected: no fix available “Fix deferred”
  • Red Hat Fuse 6.3
    fixed: vendor fix RHSA-2019:2804
  • Red Hat Fuse 7.4.0
    fixed: vendor fix RHSA-2019:2413
  • Red Hat JBoss Data Virtualization 6 jolokia-core jolokia-core
    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

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

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.0 8.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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.2, <1.6.1
1.6.1

Affected products

  • jolokia jolokia

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-352 Cross-Site Request Forgery

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.