CVE-2013-0629
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 9.0, 9.0.1, 9.0.2, and 10, when a password is not configured, allows attackers to access restricted directories via unspecified vectors, as exploited in the wild in January 2013.
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 9.0 through 9.0.2 and version 10 contains an authentication bypass vulnerability when no administrator password is configured. Unauthenticated remote attackers can access restricted directories and administrative functions via unspecified vectors. This was actively exploited in the wild in January 2013.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify ColdFusion versionCheck the installed ColdFusion version through the administrator interface or by examining the installation directory for version files. On Windows, this may be in the ColdFusion root; on Linux/Unix, check /opt/coldfusion or the installation path.Affected if Version is 9.0, 9.0.1, 9.0.2, or 10.0
-
Verify administrator password is setAttempt to access the ColdFusion Administrator console (typically at /CFIDE/administrator/) without credentials. If access is granted without a password prompt, no administrator password has been configured.Affected if No administrator password prompt appears and full administrative access is granted to unauthenticated users
-
Check for default or weak passwordReview ColdFusion security configuration files for administrator credentials. Examine whether the default blank password scenario exists or if a weak/default password is in use.Affected if Administrator account uses no password or a default/weak password
-
Review admin console exposureDetermine if the ColdFusion Administrator console is accessible from untrusted network segments. Check firewall rules and web server configuration for exposure to external networks.Affected if Administrator console is reachable from untrusted networks without network-level access controls
Environment is affected if running ColdFusion 9.0 through 9.0.2 or version 10 AND no administrator password has been configured, allowing unauthenticated access to restricted administrative functions.
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 · scopedConfigure a strong password for the ColdFusion Administrator console immediately. Ensure the administrator interface is not exposed to untrusted networks and consider network-level access controls.
ColdFusion 9.0.2 or ColdFusion 10 (apply latest updates from Adobe)
- Apply the Adobe security patch APSB13-03 (hotfix for CVE-2013-0629) from the Adobe security bulletins page
- Alternatively, apply the latest cumulative hotfix for your ColdFusion version (ColdFusion 9.0.2 Cumulative Hot Fix 3 or later, ColdFusion 10 Update 14 or later)
- After patching, ensure the ColdFusion Administrator password is properly configured - navigate to the ColdFusion Administrator and set a strong password
- Verify the patch was applied successfully by checking the ColdFusion version in the Administrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0629 — 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-0629 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