CVE intelligence and bounded remediation

CVE-2022-20774 — Cisco Ip Phone 6871 Firmware security vulnerability

High CVSS 8.1

A vulnerability in the web-based management interface of Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware could allow an unauthenticated, remote attacker to conduct a cross-site request forgery (CSRF) attack against a user of the web-based interface of an affected system. This vulnerability is due to insufficient CSRF protections for the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading an authenticated user of the interface to follow a crafted link. A successful exploit could allow the attacker to perform configuration changes on the affected device, resulting in a denial of service (DoS) condition.

Severity
High
CVSS
8.1 (3.1)
Published
2022-04-06
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-345, CWE-352

Affected products

  • cisco / ip_phone_6871_firmware
  • cisco / ip_phone_6861_firmware
  • cisco / ip_phone_6851_firmware
  • cisco / ip_phone_6841_firmware
  • cisco / ip_phone_6825_firmware
  • cisco / ip_phone_7861_firmware

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

Matched remediation archetype

Supply-chain, dependency, build, and update integrity

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

Check exposure

  • Trace affected packages, source archives, build actions, plugins, installers, and updates from declared source to deployed artifact.
  • Confirm provenance, signatures or digests, namespace ownership, lockfile resolution, registry configuration, and build-runner trust boundaries.
  • Inventory direct, transitive, vendored, generated, and bundled copies across releases and distribution channels.

Remediate safely

  • Move to a maintained trusted artifact or remove the dependency; pin immutable identities and verify provenance and integrity before use.
  • Regenerate lockfiles and artifacts in a clean isolated build, minimize build credentials and network access, and produce an updated software bill of materials.
  • Require reviewed update policy, protected publishing, and reproducible or independently attestable builds where supported.

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.