Cloud PortalApplication · Cisco

CVE-2014-0694

MEDIUM · 5.0 CVSS v2.0 Published 2014-03-14
Fix available
A fix is available. Upgrade to after 9.4.1 or later.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable 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
Intelligent Automation for Cloud (IAC) in Cisco Cloud Portal 9.4.1 and earlier includes a cryptographic key in binary files, which makes it easier for remote attackers to obtain cleartext data from an arbitrary IAC installation by leveraging knowledge of this key, aka Bug IDs CSCui34764, CSCui34772, CSCui34776, CSCui34798, CSCui34800, CSCui34805, CSCui34809, CSCui34810, CSCui34813, CSCui34814, and CSCui34818.

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 confidence

The Cisco Intelligent Automation for Cloud (IAC) product embeds a static cryptographic key directly in binary files. Because the same key is used across all installations of version 9.4.1 and earlier, any attacker who obtains this key (through binary analysis, leak, or reverse engineering) can decrypt sensitive data from any affected IAC deployment, enabling recovery of cleartext information from encrypted storage.

MitigationReplace the hardcoded cryptographic key with a properly generated unique key per installation, implement secure key management, rotate the compromised key, and re-encrypt any protected data using the new key infrastructure.

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
Cloud PortalApplication
Affected:<= 9.4.1= 9.1= 9.3= 9.3.1= 9.3.2= 9.4

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
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 checks

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

  1. Identify Cisco IAC version
    Locate and retrieve the installed version of Cisco Intelligent Automation for Cloud or Cisco Cloud Portal in your environment using the product's administrative interface, CLI, or version documentation
    Affected if The installed version is 9.1, 9.3, 9.3.1, 9.3.2, 9.4, or any version 9.4.1 or earlier
  2. Examine binary files for embedded keys
    Inspect the binary files included with the Cisco IAC installation for hardcoded cryptographic key material - look for static byte sequences or strings that represent encryption keys
    Affected if Hardcoded cryptographic key material is found embedded in any binary file distributed with the product
  3. Search for static cryptographic strings
    Use binary analysis tools to search for recognizable encryption key patterns, cryptographic constants, or key-related strings across the installation binaries
    Affected if Static cryptographic key strings or key data structures are present and identical across the installation files
  4. Compare binary key against known patterns
    Extract any embedded key material from the binaries and compare against known static key patterns used in affected versions
    Affected if A static key is found that is identical to keys used in other Cisco IAC installations of the same version

You are affected if your Cisco IAC/Cloud Portal version is 9.4.1 or earlier AND static cryptographic key material is embedded in the product binaries.

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
Upgrade available Upgrade to a release after 9.4.1
Interim mitigation

Replace the hardcoded cryptographic key with a properly generated unique key per installation, implement secure key management, rotate the compromised key, and re-encrypt any protected data using the new key infrastructure.

Fix this in Cloud Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0694 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0694 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