dbcve.org
Ip Conference Phone 7832 FirmwareOperating system · Cisco

CVE-2019-1922

HIGH · 7.5 CVSS v3.0 Published 2019-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A vulnerability in Cisco SIP IP Phone Software for Cisco IP Phone 7800 Series and 8800 Series could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected phone. The vulnerability is due to insufficient validation of input Session Initiation Protocol (SIP) packets. An attacker could exploit this vulnerability by altering the SIP replies that are sent to the affected phone during the registration process. A successful exploit could allow the attacker to cause the phone to reboot and not complete the registration process.

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

This vulnerability exists in Cisco SIP IP Phone Software for the 7800 and 8800 series phones. It stems from insufficient validation of input Session Initiation Protocol (SIP) packets. An unauthenticated remote attacker can exploit it by altering SIP replies sent to the phone during the registration process, causing the phone to reboot repeatedly and fail to complete registration.

MitigationApply the vendor-supplied software update/patch from Cisco. Until patches are available, consider network segmentation to restrict unauthorized SIP traffic to phone endpoints, and monitor for unusual registration failures indicating exploitation.

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 Conference Phone 7832 FirmwareOperating system
Affected:all versions
Ip Conference Phone 8832 FirmwareOperating system
Affected:= 11.5\(1\)= 12.5\(1\)
Ip Phone 7811 FirmwareOperating system
Affected:all versions
Ip Phone 7821 FirmwareOperating system
Affected:all versions
Ip Phone 7841 FirmwareOperating system
Affected:all versions
Ip Phone 7861 FirmwareOperating system
Affected:all versions
Ip Phone 8811 FirmwareOperating system
Affected:= 11.5\(1\)= 12.5\(1\)
Ip Phone 8841 FirmwareOperating system
Affected:= 11.5\(1\)= 12.5\(1\)

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify phone model and firmware version
    Access the phone's web interface (navigate to the phone's IP address in a browser) and check the Administration or Device section for the firmware version. Alternatively, press Settings on the phone display and look for Status or Phone Information to find the firmware version.
    Affected if The phone model is 7811, 7821, 7841, 7861, 8811, 8841, 7832, or 8832, and the firmware version is 11.5(1), 12.5(1), or any version for models listed as 'all versions'.
  2. Check for repeated reboots or registration failures
    Observe the phone display for continuous reboot cycles or error messages indicating registration failure. Check the phone's web interface Status or Call Status section for registration errors.
    Affected if The phone is repeatedly rebooting without successfully registering to the SIP call server, or displays persistent registration failures.
  3. Verify SIP registration status
    Check the phone's web interface under SIP Settings or Call Control settings to confirm the registration status. Look for indicators showing whether the phone is registered or failing to register.
    Affected if The phone shows as unregistered or unable to complete registration despite network connectivity.
  4. Review phone network exposure
    Examine network configuration to determine if the phone is accessible from untrusted networks. Check if the SIP port (UDP/TCP 5060) on the phone is exposed to networks beyond the internal voice VLAN.
    Affected if The phone's SIP interface is reachable from untrusted or outside networks, allowing unauthenticated SIP traffic to reach the device.

You are affected if you have any of the listed phone models (7800 or 8800 series) running the specified firmware versions (or any version for models listed as 'all versions') AND the phone is experiencing repeated reboots or registration failures consistent with the vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied software update/patch from Cisco. Until patches are available, consider network segmentation to restrict unauthorized SIP traffic to phone endpoints, and monitor for unusual registration failures indicating exploitation.

Fix this in Ip Conference Phone 7832 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2019-1922 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