CVE-2023-44353
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 versions 2023.5 (and earlier) and 2021.11 (and earlier) are affected by an Deserialization of Untrusted Data vulnerability that could result in Arbitrary code execution. Exploitation of this issue does not require user interaction.
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 versions 2023.5 and earlier, and 2021.11 and earlier contain a deserialization vulnerability where untrusted data is insecurely deserialized, allowing remote unauthenticated attackers to inject malicious serialized objects that execute arbitrary code on the target system without any user interaction.
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< 2021= 2021= 2023CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ColdFusion installation and versionCheck the ColdFusion administrator interface (usually at /cfadmin or /CFIDE/administrator) or inspect the version file in the ColdFusion installation directory. The version is typically displayed on the ColdFusion Administrator welcome page.Affected if The installed version is ColdFusion 2021.11 or earlier, or ColdFusion 2023.5 or earlier.
-
Confirm the ColdFusion service is network-accessibleDetermine if the ColdFusion web server connector (port 8500 by default, or port 80/443 if using IIS/Apache) is exposed to untrusted networks. Check firewall rules and network ACLs for inbound access to ColdFusion ports.Affected if ColdFusion HTTP/HTTPS endpoints are reachable from untrusted or external networks.
-
Review exposed ColdFusion endpointsIdentify which ColdFusion endpoints are listening. Common endpoints include the CFIDE directory, Web Services (WSDL), and any custom CFML endpoints. Check the server's listening ports and virtual host configurations.Affected if Any ColdFusion endpoints accept unauthenticated HTTP requests from untrusted sources.
-
Check for indicators of exploitationReview web server access logs and ColdFusion logs for suspicious patterns such as unusual serialized data in POST bodies, repeated requests to endpoints with serialized objects, or unexpected code execution indicators.
You are affected if you are running ColdFusion 2021.11 or earlier or ColdFusion 2023.5 or earlier, and your ColdFusion service is accessible over the network to unauthenticated attackers.
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 · scoped2021
Upgrade ColdFusion to the latest patched version (2023.6 or later for the 2023 track, and 2021.12 or later for the 2021 track). If immediate patching is not possible, restrict network access to ColdFusion endpoints and monitor for indicators of compromise.
ColdFusion 2021 Update 12+ or ColdFusion 2023 Update 6+
- Identify your current ColdFusion version by checking the ColdFusion Administrator or the version number displayed
- For ColdFusion 2021: Upgrade to version 2021.12 or later by applying the latest ColdFusion 2021 update from helpx.adobe.com
- For ColdFusion 2023: Upgrade to version 2023.6 or later by applying the latest ColdFusion 2023 update from helpx.adobe.com
- After upgrading, verify the new version in ColdFusion Administrator to confirm the patch was applied successfully
- Review application code for any custom deserialization implementations and ensure they do not process untrusted data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44353 — 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-2023-44353 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