7940 RouterHardware / appliance · Cisco
CVE-2007-1542
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 · uneditedUnspecified vulnerability in the Cisco IP Phone 7940 and 7960 running firmware before POS8-6-0 allows remote attackers to cause a denial of service via the Remote-Party-ID sipURI field in a SIP INVITE request. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 · low confidenceDenial of service vulnerability in Cisco IP Phone 7940 and 7960 allows remote attackers to crash the device by sending a specially crafted SIP INVITE request with a malformed Remote-Party-ID sipURI field. The vulnerability exists in firmware versions prior to POS8-6-0.
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
7940 RouterHardware / appliance
all versions
7960 RouterHardware / appliance
all versionsCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/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 device modelLocate the physical device or check network inventory for Cisco IP Phone 7940 or 7960. The model number is printed on a label on the back or bottom of the device.Affected if Device is a Cisco 7940 or 7960 IP Phone
-
Check the installed firmware versionAccess the phone's web interface (http://<phone_ip>) or press the Settings button on the device and navigate to Model Information > Firmware Version. Compare the version number to POS8-6-0.Affected if Firmware version is earlier than POS8-6-0 (for example, POS3-7-4, POS4-0-4, etc.)
-
Verify SIP protocol is enabledAccess the phone's web interface or menu and check under SIP Configuration or Proxy settings. Confirm that SIP is turned on and a SIP proxy/registrar address is configured.Affected if SIP is enabled and the phone is registered to a SIP proxy
-
Assess network exposure to SIP trafficReview firewall rules, network segments, or ACLs to determine if the phone can receive SIP INVITE requests from untrusted network sources. Check if port 5060 (SIP UDP/TCP) is open to outside networks.Affected if The device accepts SIP traffic from networks outside trusted internal sources
You are affected if you have a Cisco 7940 or 7960 IP Phone running firmware versions prior to POS8-6-0 with SIP enabled and accessible to potential attackers sending malformed INVITE requests.
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 dataUpdate Cisco IP Phone 7940/7960 firmware to version POS8-6-0 or later. If firmware updates are not feasible due to device age, consider network segmentation to restrict SIP traffic to trusted sources or implement SIP-aware firewall/IDS to detect and block malformed INVITE requests.
Fix this in 7940 Router
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1542 — 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-2007-1542 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