CVE-2012-4026
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 Pegasys P2000 server with software before 3.11 allows remote attackers to trigger false alerts via crafted packets to TCP port 41013 (aka the upload port), a different vulnerability than CVE-2012-2607.
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 confidenceThe Johnson Controls Pegasys P2000 server with software versions prior to 3.11 contains a vulnerability in its upload service on TCP port 41013. Remote attackers can send specially crafted packets to this port without authentication, causing false alerts to be generated. This is an input validation flaw in the alert/upload mechanism.
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<= 3.10all versionsCVSS 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
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/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.
-
Confirm Pegasys P2000 software installationCheck system for Johnson Controls Pegasys P2000 Server software installation by reviewing installed programs (Windows: Add/Remove Programs, Linux: package manager), or search for Pegasys-related processes or services running on the systemAffected if Pegasys P2000 Server software is installed on the system
-
Determine installed software versionCheck the installed Pegasys P2000 version by inspecting the software's About dialog, version info in its installation directory, or its service/daemon version output. Compare this version number to the affected range (<= 3.10)Affected if Installed version is 3.10 or lower (or any version if all versions are considered affected)
-
Verify TCP port 41013 accessibilityScan the system or check listening ports using netstat, ss, or a port scanner to determine if TCP port 41013 is open and listening on the Pegasys serverAffected if TCP port 41013 is open and accepting connections from unauthorized network sources
-
Check if upload service is enabledReview the Pegasys P2000 service configuration to determine if the alert/upload service on port 41013 is enabled and runningAffected if The upload service on port 41013 is enabled and exposed to the network
If the Pegasys P2000 server software is installed (any version) and TCP port 41013 is exposed and the upload service is active, the environment is affected by 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 dataUpgrade the Pegasys P2000 server software to version 3.11 or later. As a compensating control, implement network segmentation or firewall rules to restrict unauthorized access to TCP port 41013.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4026 — 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-4026 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