CVE-2007-5638 json
The Nortel UNIStim IP Softphone 2050, IP Phone 1140E, and additional Nortel products from the IP Phone, Business Communications Manager (BC…
published 2007-10-23 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-5610
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.5%
- EPSS 1.5% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
The Nortel UNIStim IP Softphone 2050, IP Phone 1140E, and additional Nortel products from the IP Phone, Business Communications Manager (BCM), and other product lines, use only 65536 different values in the 32-bit ID number field of an RUDP datagram, which makes it easier for remote attackers to guess the RUDP ID and spoof messages. NOTE: this can be leveraged for an eavesdropping attack by sending many Open Audio Stream messages.
Patch / fix
- secunia.com/advisories/27234 advisory
Exploit prediction
1.47% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- csnc.ch http://www.csnc.ch/static/advisory/csnc/nortel_IP_phone_surveillance_mode_v1.0.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/26120 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
References
-
secunia.com
/advisories/27234
third-party-advisory, patch, vendor-advisory
-
csnc.ch
/static/advisory/csnc/nortel_IP_phone_surveillance_mode_v1.0.txt
exploit
-
securityfocus.com
/bid/26120
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/37255
vdb-entry
-
osvdb.org
/41770
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42881
vdb-entry
-
securityreason.com
/securityalert/3272
third-party-advisory
-
securityfocus.com
/archive/1/482478/100/0/threaded
mailing-list
Sources
- CVE List CVE-2007-5638
- NVD CVE-2007-5638
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.