CVE-2013-1387
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 · uneditedUnspecified 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 impersonate users 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 · moderate confidenceUnspecified vulnerability in Adobe ColdFusion allows attackers to impersonate users via unknown vectors, likely involving authentication bypass. The vulnerability affects ColdFusion 9.0.x versions before Update 10/9/4 (respectively) and ColdFusion 10 before Update 9.
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= 9.0= 9.0.1= 9.0.2= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ColdFusion versionLog in to the ColdFusion Administrator console (typically at /cfadmin or /CFIDE/administrator/index.cfm) and check the version displayed on the welcome page or in the System Information section. Alternatively, check the version.txt or registry entries on the server.Affected if The version shown is 9.0, 9.0.1, 9.0.2, or 10.0 without the corresponding updates applied.
-
Determine if ColdFusion 9.0 has Update 10 appliedIn the ColdFusion Administrator, navigate to the Updates section or check the hotfix log files in the cfusion/hotfixes directory for evidence of Update 10 (also labeled as 9.0.4).Affected if Running ColdFusion 9.0 without Update 10 installed.
-
Determine if ColdFusion 9.0.1 has Update 9 appliedIn the ColdFusion Administrator, check the Updates section or examine the hotfix logs in cfusion/hotfixes for Update 9 installation evidence.Affected if Running ColdFusion 9.0.1 without Update 9 installed.
-
Determine if ColdFusion 9.0.2 has Update 4 appliedIn the ColdFusion Administrator, verify the Updates section or check the hotfix logs in cfusion/hotfixes for Update 4 (9.0.2 cumulative hotfix) installation evidence.Affected if Running ColdFusion 9.0.2 without Update 4 installed.
-
Determine if ColdFusion 10 has Update 9 appliedIn the ColdFusion Administrator, go to the Server Settings > Updates page or check the cfusion/hotfixes directory for Update 9 installation evidence.Affected if Running ColdFusion 10 without Update 9 installed.
Your environment is affected if you are running any of the listed versions (9.0, 9.0.1, 9.0.2, or 10.0) without the corresponding security update (Update 10, 9, 4, or 9 respectively) applied.
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 the corresponding Adobe ColdFusion updates: Update 10 for 9.0, Update 9 for 9.0.1, Update 4 for 9.0.2, and Update 9 for version 10.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1387 — 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-1387 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