CVE-2012-5674
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 10 before Update 5, when Internet Information Services (IIS) is used, allows attackers to cause a denial of service 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 confidenceA denial of service vulnerability exists in Adobe ColdFusion 10 versions prior to Update 5 when the server is configured to run behind Internet Information Services (IIS). The vulnerability allows remote attackers to crash the ColdFusion service via unspecified vectors, likely through malformed requests processed by the IIS-to-ColdFusion connector.
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= 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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.
-
Verify Adobe ColdFusion 10 is installedCheck the ColdFusion administrator interface or look for ColdFusion 10 installation directories on the systemAffected if ColdFusion 10 is present on the server
-
Determine the installed ColdFusion 10 version and update levelAccess the ColdFusion Administrator via the web interface (typically at /CFIDE/administrator/index.cfm) and check the version information, or run the cfusion/bin/coldfusion version command if availableAffected if The installed version is ColdFusion 10.0 prior to applying Update 5
-
Check if ColdFusion is configured to run behind IISReview the IIS configuration and verify that the IIS-to-ColdFusion connector (isapi_redirect.dll or similar) is configured to proxy requests to ColdFusion. Check IIS Manager for ColdFusion-specific handler mappings or ISAPI filtersAffected if The ColdFusion server is configured to receive requests through IIS via the connector module
-
Verify whether Update 5 has been appliedIn the ColdFusion Administrator, check the update section to see which updates are installed, or check for the presence of Update 5 specific files in the cfusion/lib directoryAffected if Update 5 has not been installed on ColdFusion 10.0
The environment is affected if Adobe ColdFusion 10.0 is installed, is configured to run behind IIS, and Update 5 has not been applied to address this vulnerability.
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 Adobe ColdFusion 10 Update 5 or later to resolve the vulnerability. Organizations should also review IIS configuration settings and consider implementing rate limiting or web application firewall rules as additional defensive measures until the patch can be applied.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-5674 — 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-2012-5674 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