CVE-2012-2607
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 · uneditedThe Johnson Controls CK721-A controller with firmware before SSM4388_03.1.0.14_BB allows remote attackers to perform arbitrary actions via crafted packets to TCP port 41014 (aka the download port).
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 confidenceThe Johnson Controls CK721-A controller with firmware versions prior to SSM4388_03.1.0.14_BB contains a vulnerability where crafted packets sent to TCP port 41014 (the download port) allow remote attackers to perform arbitrary actions on the device due to insufficient input validation or authentication.
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= ck721-a<= 03.1.0.14= 03.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 device modelDetermine if the target device is a Johnson Controls CK721-A Network Controller by checking the device label, management interface, or SNMP sysDescr value for 'CK721-A' or 'ck721-a'Affected if The device is not a CK721-A controller (different model) - the CVE does not apply
-
Check the firmware versionAccess the device management interface or use the appropriate diagnostic/management tool to retrieve the firmware version. Look for version strings such as '03.0', '03.1.0.14', or earlier. Compare against SSM4388_03.1.0.14_BBAffected if The installed firmware version is 03.0 or any version <= 03.1.0.14 (prior to SSM4388_03.1.0.14_BB)
-
Verify TCP port 41014 accessibilityScan the device for open TCP port 41014 using a port scanner (e.g., nmap -p 41014 <device_ip>) or check firewall/networkACL rules that may permit or block traffic to this portAffected if TCP port 41014 (the download port) is exposed and reachable from an untrusted network or host
The device is affected if it is a CK721-A controller running firmware version 03.0 or <= 03.1.0.14 AND TCP port 41014 is accessible on the network.
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 dataUpdate the CK721-A controller firmware to version SSM4388_03.1.0.14_BB or later. If immediate patching is not possible, implement network segmentation and firewall rules to restrict access to TCP port 41014 to only trusted management stations.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2607 — 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-2607 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