CVE intelligence and bounded remediation

CVE-2022-20817 — Cisco Unified Ip Phone 6911 Firmware security vulnerability

High CVSS 7.4

A vulnerability in Cisco Unified IP Phones could allow an unauthenticated, remote attacker to impersonate another user's phone if the Cisco Unified Communications Manager (CUCM) is in secure mode. This vulnerability is due to improper key generation during the manufacturing process that could result in duplicated manufactured keys installed on multiple devices. An attacker could exploit this vulnerability by performing a machine-in-the-middle attack on the secure communication between the phone and the CUCM. A successful exploit could allow the attacker to impersonate another user's phone. This vulnerability cannot be addressed with software updates. There is a workaround that addresses this vulnerability.

Severity
High
CVSS
7.4 (3.1)
Published
2022-06-15
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-338

Affected products

  • cisco / unified_ip_phone_6911_firmware
  • cisco / unified_ip_phone_6921_firmware
  • cisco / unified_ip_phone_6941_firmware
  • cisco / unified_ip_phone_6945_firmware
  • cisco / unified_ip_phone_6961_firmware
  • cisco / unified_ip_phone_8941_firmware

Showing 6 representative product identities from 11 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cryptography, certificate, signature, and channel validation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
  • Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
  • Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.

Remediate safely

  • Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
  • Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
  • Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.