Ip Phone 6871 FirmwareOperating system · Cisco
CVE-2022-20774
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 · uneditedA 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.
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 confidenceCSRF vulnerability in Cisco IP Phone 6800, 7800, and 8800 Series web-based management interface allows unauthenticated remote attackers to trick authenticated users into clicking crafted links that perform unauthorized configuration changes, resulting in denial of service.
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
Ip Phone 6871 FirmwareOperating system
< 11.3.5
Ip Phone 6861 FirmwareOperating system
< 11.3.5
Ip Phone 6851 FirmwareOperating system
< 11.3.5
Ip Phone 6841 FirmwareOperating system
< 11.3.5
Ip Phone 6825 FirmwareOperating system
< 11.3.5
Ip Phone 7861 FirmwareOperating system
< 11.3.5
Ip Phone 7841 FirmwareOperating system
< 11.3.5
Ip Phone 7832 FirmwareOperating system
< 11.3.5CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the phone modelAccess the web-based management interface at the phone's IP address and locate the model number, or check the physical device labelAffected if Model is one of the affected series: 6825, 6841, 6851, 6861, 6871, 7832, 7841, or 7861
-
Check the installed firmware versionLog into the phone's web interface and navigate to the firmware or system information page to view the current firmware versionAffected if Firmware version is less than 11.3.5 (for example, 11.3.4, 11.2.x, etc.)
-
Verify if web-based management is enabledAccess the phone's web interface using its IP address from a browser; if a login page loads, the web interface is enabledAffected if The web-based management interface is accessible and a login page is served
If the phone model is in the affected list, the firmware version is below 11.3.5, AND the web-based management interface is enabled, the environment is vulnerable to this CSRF flaw.
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.
dbcve · scoped11.3.5
Apply Cisco's firmware patch when released; until then, warn users not to click untrusted links while logged into the phone management interface.
Firmware version 11.3.5 or later for Cisco IP Phone 6800, 7800, and 8800 Series with Multiplatform Firmware
- 1. Access the web-based management interface of the affected Cisco IP Phone (6800, 7800, or 8800 Series with Multiplatform Firmware)
- 2. Navigate to the Administration > Firmware Upgrade or similar firmware management section
- 3. Download the firmware version 11.3.5 or later from the Cisco Software Download Center (tools.cisco.com)
- 4. Upload the firmware file to the device through the web interface
- 5. Confirm the upgrade completes successfully
- 6. Verify the device is running firmware version 11.3.5 or later by checking the device status page
- 7. After upgrade, clear browser session cookies and re-authenticate to ensure no stale CSRF tokens remain
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ip Phone 6871 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20774 — 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-2022-20774 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