CVE-2013-3350
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 · uneditedAdobe ColdFusion 10 before Update 11 allows remote attackers to call ColdFusion Components (CFC) public methods via WebSockets.
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 confidenceAdobe ColdFusion 10 before Update 11 contains a vulnerability that allows unauthenticated remote attackers to invoke ColdFusion Components (CFC) public methods through WebSocket connections. This enables attackers to potentially execute arbitrary code or access sensitive business logic without authentication.
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= 10.0CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 10 installationLocate the ColdFusion installation directory and check the version file, or access the ColdFusion Administrator and navigate to the About pageAffected if ColdFusion 10 is not installed or a different major version is present
-
Check installed update versionAccess ColdFusion Administrator > Server Updates > Updates Applied, or check the hotfix summary file in the cf10 installation directory for the update levelAffected if The installed update is earlier than Update 11 (e.g., Update 10, Update 9, or no updates applied)
-
Verify WebSocket is enabledIn ColdFusion Administrator, go to Server Settings > WebSocket Settings and check if WebSocket endpoints are enabled, or inspect the server's web.xml for WebSocket servlet configurationAffected if WebSocket functionality is enabled on the server
-
Check for CFC access via WebSocketReview any configured WebSocket gateways or CFC invokers in the application, and examine the server logs for incoming WebSocket connection attempts to CFC endpointsAffected if CFC methods can be invoked through WebSocket connections without authentication
The environment is affected if ColdFusion 10 is running with an update earlier than Update 11 AND WebSocket is enabled, allowing unauthenticated attackers to invoke CFC methods and potentially execute arbitrary code.
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.
dbcve · scopedApply ColdFusion 10 Update 11 or later to patch the WebSocket deserialization vulnerability. If immediate patching is not possible, consider disabling WebSocket endpoints or restricting network access to the ColdFusion server.
ColdFusion 10 Update 11 or later
- Access the Adobe ColdFusion downloads page or Adobe Support Portal
- Download ColdFusion 10 Update 11 (or later) from the available patches
- Apply the update by running the installer on the ColdFusion 10 server
- Follow Adobe's standard update installation procedures
- Restart the ColdFusion Application Server services after installation
- Verify the update was successfully applied by checking the ColdFusion administrator or version info
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3350 — 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-2013-3350 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