ColdfusionApplication · Adobe

CVE-2013-1388

HIGH · 7.5 CVSS v2.0 Published 2013-04-10
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
Unspecified vulnerability in Adobe ColdFusion 9.0 before Update 10, 9.0.1 before Update 9, 9.0.2 before Update 4, and 10 before Update 9 allows attackers to obtain administrator-console access via unknown vectors.

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

Unspecified vulnerability in Adobe ColdFusion allows attackers to obtain administrator-console access via unknown vectors. The vulnerability affects versions 9.0 before Update 10, 9.0.1 before Update 9, 9.0.2 before Update 4, and 10 before Update 9.

MitigationApply the vendor-supplied updates: Update 10 for ColdFusion 9.0, Update 9 for 9.0.1, Update 4 for 9.0.2, and Update 9 for ColdFusion 10.

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:= 9.0= 9.0.1= 9.0.2= 10.0

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Check installed ColdFusion version via admin console
    Log into the ColdFusion Administrator console (typically at /CFIDE/administrator/) and navigate to the System Information or Settings page to view the exact version number and installed updates.
    Affected if The displayed version is 9.0 without Update 10, 9.0.1 without Update 9, 9.0.2 without Update 4, or 10 without Update 9.
  2. Check ColdFusion version via registry (Windows)
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ColdFusion\Install_Jetty or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\ColdFusion\CurrentVersion to find the installed version and build number.
    Affected if The version key shows 9.0.x or 10.0.x without the corresponding update build number.
  3. Check version file in installation directory
    Locate the coldfusion.jar file in the ColdFusion installation lib directory (typically {cfusion_home}/lib/) and inspect the manifest or version properties for the build date and update level.
    Affected if The build information predates the specific update release dates for your version branch.
  4. Check for administrator session vulnerability
    Review ColdFusion administrator logs and session configuration files (under {cfusion_home}/lib/ or {cfusion_home}/wwwroot/WEB-INF/) for unauthorized access attempts or unexpected administrator accounts.
    Affected if Unauthorized administrator access is detected or unknown admin accounts exist.
  5. Verify update patch installation
    Check for the presence of the hotfix update files in the ColdFusion updates directory (typically {cfusion_home}/lib/updates/) and compare against the required update numbers (10 for 9.0, 9 for 9.0.1, 4 for 9.0.2, 9 for 10).
    Affected if The required update number for your specific version is not present in the updates directory.

Your ColdFusion installation is affected if it runs version 9.0 before Update 10, 9.0.1 before Update 9, 9.0.2 before Update 4, or 10 before Update 9.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied updates: Update 10 for ColdFusion 9.0, Update 9 for 9.0.1, Update 4 for 9.0.2, and Update 9 for ColdFusion 10.

Fix this in Coldfusion Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1388 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-1388 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