dbcve.org
ColdfusionApplication · Adobe

CVE-2024-34112

HIGH · 7.5 CVSS v3.1 Published 2024-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
ColdFusion versions 2023u7, 2021u13 and earlier are affected by an Improper Access Control vulnerability that could result in arbitrary file system read. An attacker could exploit this vulnerability to gain unauthorized access to sensitive files or data. 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 confidence

ColdFusion versions 2023u7, 2021u13 and earlier contain an Improper Access Control vulnerability that allows unauthenticated attackers to read arbitrary files from the file system without user interaction, potentially exposing sensitive configuration, credentials, or data.

MitigationApply the available security update from Adobe to upgrade to patched ColdFusion versions (2023u8+ and 2021u14+), or implement network-level restrictions to limit ColdFusion server exposure.

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:= 2021= 2023

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 installed ColdFusion version
    Access the ColdFusion Administrator interface or check the version file in the ColdFusion installation directory. The version is typically displayed on the Administrator login page or in the 'Server Settings > Server Updates' section.
    Affected if The installed version is 2023 Update 7 or earlier, or 2021 Update 13 or earlier.
  2. Confirm ColdFusion edition and update level
    Locate the coldfusion-version.txt or similar version file in the installation directory, or run the cfadmin API to query the current update level. Compare the exact version string against the affected ranges.
    Affected if The version string shows 2023.u7 or lower, or 2021.u13 or lower.
  3. Check for unauthorized file access attempts
    Review ColdFusion server logs (typically in /logs or the logs directory) for unusual or repeated requests to file endpoints, especially patterns that resemble directory traversal or file read operations.
    Affected if Log entries show unauthenticated requests to file paths outside the web root, or suspicious file read activity from external IPs.
  4. Verify network exposure of ColdFusion services
    Confirm whether the ColdFusion ports (default 8500, 8501, or configured HTTP/HTTPS ports) are directly accessible from untrusted networks or the internet.
    Affected if The ColdFusion admin interfaces or endpoints are exposed to the public internet without authentication barriers.

A system is affected if it runs Adobe ColdFusion 2023 Update 7 or earlier, or ColdFusion 2021 Update 13 or earlier, and the vulnerable file access endpoint is reachable.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the available security update from Adobe to upgrade to patched ColdFusion versions (2023u8+ and 2021u14+), or implement network-level restrictions to limit ColdFusion server exposure.

Recommended fix Moderate confidence

ColdFusion 2023 Update 8+ or ColdFusion 2021 Update 14+

  1. 1. Back up your ColdFusion installation and any critical data before applying updates.
  2. 2. Identify your current ColdFusion version by accessing the ColdFusion Administrator console.
  3. 3. For ColdFusion 2023: Upgrade to ColdFusion 2023 Update 8 or later (the first version after the vulnerable u7 release).
  4. 4. For ColdFusion 2021: Upgrade to ColdFusion 2021 Update 14 or later (the first version after the vulnerable u13 release).
  5. 5. Download the appropriate update from the Adobe ColdFusion downloads page (helpx.adobe.com).
  6. 6. Apply the update following Adobe's standard ColdFusion update installation procedures.
  7. 7. After updating, verify the ColdFusion services start correctly and test critical applications.
  8. 8. Confirm the update was successful by checking the version in ColdFusion Administrator.
Caveat Standard ColdFusion updates typically do not introduce breaking changes, but always review the update release notes for any configuration or compatibility notes before applying.

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

Fix this in Coldfusion Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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