CVE-2020-3767
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 · uneditedColdFusion versions ColdFusion 2016, and ColdFusion 2018 have an insufficient input validation vulnerability. Successful exploitation could lead to application-level denial-of-service (dos).
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 · moderate confidenceColdFusion 2016 and 2018 contain an insufficient input validation vulnerability that allows remote attackers to cause application-level denial of service. The vulnerability stems from improper validation of user-supplied input, which can trigger a DoS condition when crafted requests are processed by the ColdFusion server.
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= 2016= 2018CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm ColdFusion installationAccess the ColdFusion Administrator interface at /CFIDE/administrator/ or check for ColdFusion services running on the serverAffected if ColdFusion is not installed or not accessible
-
Identify installed ColdFusion versionIn the ColdFusion Administrator, navigate to the Settings or About page to view the exact version number. On Windows, also check the registry key HKLM\SOFTWARE\Adobe\ColdFusion\CurrentVersion or inspect the version info in the ColdFusion installation directoryAffected if Version displays as 2016 or 2018 (any update within these releases)
-
Verify patch statusIn the ColdFusion Administrator, check the Security Updates section or review installed hotfixes. You can also examine the file {cfusion.home}/lib/hotfixes/ for recent patch filesAffected if No security patches for CVE-2020-3767 are installed or listed as applied
-
Check for DoS exposureReview server configuration files (server.xml, neo-runtime.xml) for input validation settings and ensure user-supplied input is processed without timeout restrictions on critical endpointsAffected if Input validation is minimal or absent on user-facing endpoints processing untrusted data
The environment is affected if Adobe ColdFusion 2016 or 2018 is running without the CVE-2020-3767 security patch applied and user-facing endpoints accept unvalidated input.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Adobe's security patches for CVE-2020-3767 for ColdFusion 2016 and 2018. As compensating controls, implement strict input validation on all user-facing endpoints and consider rate limiting to mitigate DoS attempts until patches are fully deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3767 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3767 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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