Voip Phone Cp 7940Hardware / appliance · Cisco
CVE-2002-0882
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 · uneditedThe web server for Cisco IP Phone (VoIP) models 7910, 7940, and 7960 allows remote attackers to cause a denial of service (reset) and possibly read sensitive memory via a large integer value in (1) the stream ID of the StreamingStatistics script, or (2) the port ID of the PortInformation script.
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 · moderate confidenceThe embedded web server in Cisco IP Phone models 7910, 7940, and 7960 fails to properly validate large integer values in HTTP request parameters. Specifically, the stream ID parameter in the StreamingStatistics script and the port ID parameter in the PortInformation script accept oversized values that cause the device to reset (denial of service) and may allow attackers to read sensitive memory contents from adjacent memory locations.
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
Voip Phone Cp 7940Hardware / appliance
= 3.0= 3.1= 3.2
Skinny Client Control Protocol SoftwareOperating system
= 3.0= 3.1= 3.2CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:N/A:P
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 Cisco IP Phone modelCheck the device label, CDP neighbors, or DHCP options to confirm the model is 7910, 7940, or 7960Affected if The device is a Cisco IP Phone 7910, 7940, or 7960
-
Check the firmware versionAccess the phone's web interface or use TFTP to retrieve the firmware version file; compare against 3.0, 3.1, or 3.2Affected if The firmware version is 3.0, 3.1, or 3.2
-
Verify the embedded HTTP web server is enabledAttempt to access the phone's web interface via HTTP on port 80 or the configured management portAffected if The HTTP service responds and displays the phone's management page
-
Confirm access to vulnerable scriptsAttempt HTTP requests to /StreamingStatistics and /PortInformation endpoints on the phone's web serverAffected if These scripts are accessible and accept integer parameters without validation
You are affected if you have a Cisco IP Phone 7910, 7940, or 7960 running firmware version 3.0, 3.1, or 3.2 with the embedded HTTP web server enabled and accessible.
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.
From vendor dataRestrict network access to the phone management interfaces using ACLs or network segmentation. Due to the age of these devices (2002 vulnerability), strongly consider replacing them with current models as no patches are expected. If continued use is mandatory, isolate these phones in a dedicated VLAN with strict firewall rules.
Fix this in Voip Phone Cp 7940
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0882 — 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-2002-0882 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