dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Mar 2025.
ColdfusionApplication · Adobe

CVE-2017-3066

CRITICAL · 9.8 CVSS v3.1 Published 2017-04-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
Adobe ColdFusion 2016 Update 3 and earlier, ColdFusion 11 update 11 and earlier, ColdFusion 10 Update 22 and earlier have a Java deserialization vulnerability in the Apache BlazeDS library. Successful exploitation could lead to arbitrary code execution.

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

Adobe ColdFusion versions 10, 11, and 2016 contain a Java deserialization vulnerability in the included Apache BlazeDS library. Attackers can exploit this by sending specially crafted serialized Java objects to vulnerable endpoints, leading to arbitrary code execution on the affected server.

MitigationApply the appropriate ColdFusion update (ColdFusion 2016 Update 4+, ColdFusion 11 Update 12+, or ColdFusion 10 Update 23+) to patch the vulnerable BlazeDS library. Consider network segmentation and disabling unnecessary BlazeDS endpoints as additional hardening.

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
ColdfusionApplication
Affected:= 10.0= 11.0= 2016

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.1/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 ColdFusion installation
    Locate the ColdFusion installation directory. On Windows, common paths are C:\ColdFusion2016\, C:\ColdFusion11\, or C:\ColdFusion10\. On Linux/Unix, look in /opt/coldfusion/ or /opt/ColdFusion/.
    Affected if Adobe ColdFusion is not installed on the system.
  2. Check ColdFusion version via administrator
    Access the ColdFusion Administrator interface at /cfide/administrator/ and view the System Information page, or check the version.xml file in the lib directory of the installation.
    Affected if The installed version is 2016 Update 3 or earlier, 11 Update 11 or earlier, or 10 Update 22 or earlier.
  3. Check version from command line
    Run the ColdFusion version checker if available, or examine the manifest file in the ColdFusion installation directory for the exact update level.
    Affected if The reported version falls within the affected ranges (10.x up to Update 22, 11.x up to Update 11, or 2016 up to Update 3).
  4. Verify BlazeDS endpoint exposure
    Check if the BlazeDS endpoint is accessible by attempting to access /flex/amf/ or /messagebroker/amf on the ColdFusion server via HTTP/HTTPS.
    Affected if The BlazeDS endpoint is exposed and accepts AMF (Action Message Format) requests without authentication.

The system is affected if Adobe ColdFusion version 10, 11, or 2016 is installed with an update level at or below the thresholds (Update 22, Update 11, or Update 3 respectively) AND the BlazeDS endpoint is accessible over the network.

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
Patch available Apply the vendor patch
Vendor patch helpx.adobe.com →
Interim mitigation

Apply the appropriate ColdFusion update (ColdFusion 2016 Update 4+, ColdFusion 11 Update 12+, or ColdFusion 10 Update 23+) to patch the vulnerable BlazeDS library. Consider network segmentation and disabling unnecessary BlazeDS endpoints as additional hardening.

Recommended fix Moderate confidence

ColdFusion 10 Update 23 or later; ColdFusion 11 Update 12 or later; ColdFusion 2016 Update 4 or later; or migrate to the latest ColdFusion release (2021/2023)

  1. 1. Identify your current ColdFusion version and update level by accessing the ColdFusion Administrator console or checking the version.txt file in the installation directory.
  2. 2. For ColdFusion 10 users: Apply Update 23 or later, which includes the security patch for the BlazeDS deserialization vulnerability.
  3. 3. For ColdFusion 11 users: Apply Update 12 or later, which includes the security patch for the BlazeDS deserialization vulnerability.
  4. 4. For ColdFusion 2016 users: Apply Update 4 or later, which includes the security patch for the BlazeDS deserialization vulnerability.
  5. 5. Alternatively, consider upgrading to the latest available ColdFusion version for your product line to ensure all security patches are applied.
  6. 6. After applying the update, restart the ColdFusion application server services.
  7. 7. Verify the update was successful by checking the ColdFusion Administrator or version information.
Caveat Standard update apply risks apply - ensure backups of configuration files and test in staging before production deployment

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

Fix this in Coldfusion Exploited in the wild — priority engagement
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA4.0 h
38.0 hours of engineering $6,480
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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