dbcve.org
Webarchive AgentApplication · Jolokia

CVE-2018-1000130

HIGH · 8.1 CVSS v3.0 Published 2018-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A JNDI Injection vulnerability in Jolokia agent version 1.3.7 proxy mode allows remote attackers to run arbitrary Java code by manipulating JNDI lookups, potentially through malicious LDAP or RMI references.

MitigationUpgrade Jolokia agent to a patched version (1.3.8 or later) that addresses the JNDI injection vulnerability, and if possible, disable proxy mode if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Webarchive AgentApplication
Affected:= 1.3.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Jolokia installation and determine version
    Check for jolokia.war or jolokia-agent.jar files in your deployment directories, application lib folders, or runtime classpath. Review your build artifacts or dependency management for the Jolokia version number.
    Affected if The installed version is exactly 1.3.7
  2. Verify proxy mode configuration
    Examine Jolokia configuration files (typically jolokia.properties or init parameters in web.xml) for proxy-related settings. Look for parameters such as 'proxy', 'agentType', or custom proxy configuration that enable proxy functionality.
    Affected if Proxy mode is explicitly enabled or configured in the Jolokia agent settings
  3. Confirm proxy HTTP endpoint is exposed
    Check if an HTTP/HTTPS endpoint for the Jolokia proxy is accessible and listening. This typically involves reviewing your web server or servlet container configuration for Jolokia proxy servlet mappings.
    Affected if A proxy endpoint is actively exposed and reachable

You are affected only if you have Jolokia version 1.3.7 AND proxy mode is enabled and accessible, as the JNDI injection only manifests when the proxy functionality is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Jolokia agent to a patched version (1.3.8 or later) that addresses the JNDI injection vulnerability, and if possible, disable proxy mode if not required.

Fix this in Webarchive Agent Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000130 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1000130 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data