CVE-2016-1319
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 · uneditedCisco Unified Communications Manager (aka CallManager) 9.1(2.10000.28), 10.5(2.10000.5), 10.5(2.12901.1), and 11.0(1.10000.10); Unified Communications Manager IM & Presence Service 10.5(2); Unified Contact Center Express 11.0(1); and Unity Connection 10.5(2) store a cleartext encryption key, which allows local users to obtain sensitive information via unspecified vectors, aka Bug ID CSCuv85958.
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 confidenceCisco Unified Communications Manager and related products (Unified CM IM&P, UCCX, Unity Connection) store encryption keys in cleartext on the local filesystem. Local users with file system access can read these unencrypted keys and potentially decrypt sensitive communications data. The CVSS vector indicates local attack vector (AV:L), low privileges required (PR:L), and high confidentiality impact (C:H).
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= snv_124= t-ms14jakucb-1102.5< 2.50\(aazi.0\)c0= 3.08CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the affected product and firmware versionDetermine the exact product model and current firmware/software version installed in your environment. For Sun Opensolaris, run 'uname -a' or check system version. For Samsung X14j, check system information or BIOS version. For Zyxel Gs1900-10HP, use the web interface or CLI 'show version' command. For Zzinc Keymouse, check the device firmware through its configuration software.Affected if The installed version matches snv_124 for Sun Opensolaris, t-ms14jakucb-1102.5 for Samsung X14j, or is below 2.50(aazi.0)c0 for Zyxel Gs1900-10HP, or is exactly 3.08 for Zzinc Keymouse Firmware
-
Locate potential key storage locations on the filesystemSearch the local filesystem for encryption key files. Common paths to inspect include /etc, /var, /config, or product-specific data directories. Use commands like 'find / -name *key* -o -name *pem* -o -name *cert* 2>/dev/null' to locate key-related files. Check product-specific directories for stored credentials or key material.Affected if Key files are found in world-readable or group-readable locations on the filesystem
-
Verify file permissions on encryption key storage locationsRun 'ls -la' on directories where keys are stored to check permissions. Examine whether files containing keys have overly permissive access rights such as 644, 666, or world-readable settings. Check if unprivileged local users can read these files.Affected if Encryption key files have permissions allowing read access by non-privileged users (e.g., mode 644, 655, or world-readable)
-
Inspect key files for cleartext storageUse 'cat' or a hex editor to examine the content of identified key files. Check whether the key material appears in plaintext rather than being encrypted or hashed. Look for readable ASCII key strings, certificate private keys (BEGIN RSA PRIVATE KEY), or symmetric key data.Affected if Encryption keys are stored in plaintext (readable ASCII or binary key data without encryption wrapping)
-
Check if local user access to filesystem is not restrictedReview system access controls to determine if low-privilege local users can navigate and read from directories where keys are stored. Verify that file system access is not limited to administrator or root-only accounts.Affected if Local users with low privileges can access the directories or files containing the encryption keys
You are affected if your product version matches one of the affected versions listed AND encryption keys are stored in readable plaintext files accessible to low-privilege local users on the filesystem.
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 data2.50
Apply vendor-supplied patches when available; otherwise restrict local file system access to privileged accounts only and rotate encryption keys after applying updates. Coordinate with Cisco TAC for version-specific patch availability.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1319 — 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-2016-1319 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