dbcve.org
1000 Ccu GmsHardware / appliance · Pacom

CVE-2014-3260

HIGH · 7.5 CVSS v3.0 Published 2015-12-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Pacom 1000 CCU and RTU GMS devices allow remote attackers to spoof the controller-to-base data stream by leveraging improper use of cryptography.

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 confidence

The Pacom 1000 CCU and RTU GMS devices have a vulnerability where improper use of cryptography in the controller-to-base communication channel allows remote attackers to spoof the data stream. This means attackers can potentially impersonate the controller or manipulate data in transit due to weak, absent, or incorrectly implemented cryptographic protections.

MitigationIf a vendor firmware update is available, apply it to remediate the cryptographic weaknesses. In the interim, implement network segmentation to isolate the affected devices and add additional authentication layers to protect the controller-to-base communication channel.

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
1000 Ccu GmsHardware / appliance
Affected:all versions
Rtu GmsHardware / appliance
Affected:all versions

CVSS 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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pacom 1000 CCU GMS devices in your environment
    Inventory your industrial control system (ICS) network to locate any Pacom 1000 CCU (Central Control Unit) GMS devices. Check device labels, network scans, or asset management records for this specific model.
    Affected if Any Pacom 1000 CCU GMS device is found in the environment, as all versions are affected.
  2. Identify Pacom RTU GMS devices in your environment
    Inventory your industrial control system (ICS) network to locate any Pacom RTU (Remote Terminal Unit) GMS devices. Check device labels, network scans, or asset management records for this specific model.
    Affected if Any Pacom RTU GMS device is found in the environment, as all versions are affected.
  3. Verify controller-to-base communication is in use
    Examine the network configuration and traffic between the Pacom devices and their base station. Determine if the devices are transmitting data to a base/server controller using the communication channel.
    Affected if The Pacom devices are actively communicating with a base station, as this is the communication channel described as vulnerable.
  4. Check for cryptographic protection on the communication channel
    Inspect the communication protocol configuration between the Pacom devices and the base. Look for encryption settings, TLS/SSL implementation, or other cryptographic controls on the data-in-transit between controller and base.
    Affected if No encryption, weak encryption, or improperly configured cryptographic protection is found on the controller-to-base communication channel.

If Pacom 1000 CCU GMS or Pacom RTU GMS devices exist in your environment and use controller-to-base communication, you are affected by this vulnerability since all versions lack proper cryptographic protections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If a vendor firmware update is available, apply it to remediate the cryptographic weaknesses. In the interim, implement network segmentation to isolate the affected devices and add additional authentication layers to protect the controller-to-base communication channel.

Fix this in 1000 Ccu Gms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3260 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3260 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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