dbcve.org
Ip Conference Phone 7832 FirmwareOperating system · Cisco

CVE-2019-1635

HIGH · 7.5 CVSS v3.1 Published 2019-05-03
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 the call-handling functionality of Session Initiation Protocol (SIP) Software for Cisco IP Phone 7800 Series and 8800 Series could allow an unauthenticated, remote attacker to cause an affected phone to reload unexpectedly, resulting in a temporary denial of service (DoS) condition. The vulnerability is due to incomplete error handling when XML data within a SIP packet is parsed. An attacker could exploit this vulnerability by sending a SIP packet that contains a malicious XML payload to an affected phone. A successful exploit could allow the attacker to cause the affected phone to reload unexpectedly, resulting in a temporary 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 confidence

A vulnerability in the SIP call-handling functionality of Cisco IP Phone 7800 Series and 8800 Series exists due to incomplete error handling during XML data parsing within SIP packets. An unauthenticated remote attacker can send a specially crafted SIP packet containing a malicious XML payload to trigger an unexpected reload of the affected phone, causing temporary denial of service.

MitigationApply the Cisco-provided software update/patch for the SIP firmware on affected IP phones. Until patched, consider network-level filtering of untrusted SIP traffic or restricting SIP access to trusted sources via VLAN segmentation or firewall rules.

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:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Conference Phone 8832 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 7811 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 7821 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 7841 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 7861 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 8811 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1
Ip Phone 8841 FirmwareOperating system
Affected:= 9.3\(4\)sr3= 10.3\(1\)sr4b= 11.0\(4\)sr2= 12.1\(1\)sr1

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.1/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 the phone model
    Physically inspect the phone or check the administrative web interface (Settings > Device Settings > Model Information) to confirm the model is one of: 7811, 7821, 7841, 7861, 8811, 8841, 7832, or 8832.
    Affected if The phone model matches one of the affected models listed in the CVE.
  2. Check the firmware version
    Access the phone's web interface (typically https://<phone_ip>) and navigate to Info > Device Information, or use the phone keypad: Settings > Device Settings > Firmware Version. Compare the displayed version against the affected versions: 9.3(4)sr3, 10.3(1)sr4b, 11.0(4)sr2, or 12.1(1)sr1.
    Affected if The installed firmware version exactly matches one of the four versions listed in the CVE.
  3. Confirm SIP is enabled
    Check the phone's configuration through the administrative web interface under Call Control > SIP Settings, or via the phone keypad: Settings > Network Setup > SIP Settings. Verify that SIP is enabled (not disabled).
    Affected if SIP protocol is enabled on the phone, as the vulnerability resides in the SIP call-handling functionality.
  4. Verify network accessibility of SIP port
    Check if UDP/TCP port 5060 (default SIP port) is open and reachable from untrusted networks by scanning the phone's IP address or reviewing firewall rules.
    Affected if The SIP port (5060) is accessible from untrusted network segments, allowing an attacker to send malicious SIP packets.

The phone is affected if it is one of the listed models, runs exactly one of the four vulnerable firmware versions, has SIP enabled, and has SIP port 5060 reachable from untrusted sources.

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 Cisco-provided software update/patch for the SIP firmware on affected IP phones. Until patched, consider network-level filtering of untrusted SIP traffic or restricting SIP access to trusted sources via VLAN segmentation or firewall rules.

Fix this in Ip Conference Phone 7832 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1635 — 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-1635 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