dbcve.org
EsigateApplication

CVE-2018-1000854

CRITICAL · 9.8 CVSS v3.0 Published 2018-12-20
Fix available
A fix is available. Upgrade to after 5.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
esigate.org esigate version 5.2 and earlier contains a CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in ESI directive with user specified XSLT that can result in Remote Code Execution. This attack appear to be exploitable via Use of another weakness in backend application to reflect ESI directives. This vulnerability appears to have been fixed in 5.3.

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

esigate versions 5.2 and earlier contain an improper neutralization vulnerability (CWE-74) in ESI directive processing that allows attackers to specify malicious XSLT transformations. This leads to remote code execution when the vulnerable esigate instance processes ESI directives containing user-controlled XSLT content, typically exploiting a separate reflection vulnerability in the backend application to inject the malicious directives.

MitigationUpgrade to esigate version 5.3 or later. Additionally, implement strict input validation on any backend application that could reflect ESI directives, and restrict or disable user-controlled XSLT processing in ESI configurations.

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
EsigateApplication
Affected:<= 5.2

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/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. Identify if esigate is present in your environment
    Check for esigate installation or running processes. Look for esigate JAR files, WAR files, or running Java processes with 'esigate' in the name or arguments.
    Affected if esigate is installed and running in your environment
  2. Determine the installed esigate version
    Check the esigate version by examining the JAR/WAR file name, the manifest file (META-INF/MANIFEST.MF) inside the esigate artifact, or by querying the esigate admin/status endpoint if available.
    Affected if The version is 5.2 or any version lower than 5.3 (e.g., 5.2, 5.1, 5.0, etc.)
  3. Verify ESI directive processing is enabled
    Examine the esigate configuration files (typically esigate.xml or similar configuration files in the deployment) to confirm that ESI processing is enabled. Look for 'esi' or 'ESI' related configuration settings.
    Affected if ESI processing is enabled in the esigate configuration
  4. Check for user input reflection into ESI directives
    Review your backend application code and esigate configuration to identify if user-supplied input can be reflected into ESI directives. Look for any endpoints or parameters that echo back user data that could contain ESI tags.
    Affected if User-controlled input can reach the ESI processing pipeline without proper sanitization

Your environment is affected if you are running esigate version 5.2 or earlier with ESI processing enabled and user input can reach the ESI directive processor.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.2
Interim mitigation

Upgrade to esigate version 5.3 or later. Additionally, implement strict input validation on any backend application that could reflect ESI directives, and restrict or disable user-controlled XSLT processing in ESI configurations.

Recommended fix High confidence

5.3

  1. 1. Identify the current Esigate installation and verify the version is <= 5.2
  2. 2. Backup all existing Esigate configuration files, including any custom ESI templates and XSLT files
  3. 3. Download Esigate version 5.3 from the official GitHub repository (github.com/esigate/esigate)
  4. 4. Replace the existing Esigate installation with version 5.3 files
  5. 5. Restore the backed-up configuration files to the new installation
  6. 6. Restart the Esigate service
  7. 7. Verify that Esigate 5.3 is running and the service is operational
  8. 8. Test that ESI processing works correctly with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Esigate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1000854 — 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-1000854 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