| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Avaya 4602SW IP Phone up to R2.2. It has been classified as critical. The impacted element is an unknown function. The manipulation of the argument cnonce leads to Remote Code Execution. This vulnerability is referenced as CVE-2007-3319. No exploit is available.
Details
A vulnerability was found in Avaya 4602SW IP Phone up to R2.2 (IP Phone Software). It has been rated as critical. This issue affects an unknown code block. The manipulation of the argument cnonce with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Avaya 4602SW IP Phone (Model 4602D02A) with 2.2.2 and earlier SIP firmware does not use the cnonce parameter in the Authorization header of SIP requests during MD5 digest authentication, which allows remote attackers to conduct man-in-the-middle attacks and hijack or intercept communications.
The weakness was published 06/19/2007 by ViPeR (Website). The advisory is shared at sipera.com. The identification of this vulnerability is CVE-2007-3319. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at X-Force (34972), SecurityFocus (BID 24539†), OSVDB (38115†), Secunia (SA25747†) and Vulnerability Center (SBV-23208†). Similar entries are available at VDB-37388, VDB-37387 and VDB-37386. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.avaya.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Remote Code ExecutionCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/19/2007 🔍06/19/2007 🔍
06/19/2007 🔍
06/21/2007 🔍
06/21/2007 🔍
06/26/2007 🔍
08/13/2009 🔍
03/15/2015 🔍
07/20/2021 🔍
Sources
Vendor: avaya.comAdvisory: sipera.com
Researcher: ViPeR
Status: Not defined
Confirmation: 🔍
CVE: CVE-2007-3319 (🔍)
GCVE (CVE): GCVE-0-2007-3319
GCVE (VulDB): GCVE-100-37385
X-Force: 34972
SecurityFocus: 24539 - Avaya 4602SW SIP Phone Cnonce Parameter Authentication Spoofing Vulnerability
Secunia: 25747
OSVDB: 38115 - Avaya 4602SW IP Phone SIP Authorization MiTM Weakness
Vulnerability Center: 23208 - Avaya 4602SW IP Phone SIP Firmware 2.2.2 and Earlier Hijacking and Interception of Communications, High
See also: 🔍
Entry
Created: 03/15/2015 15:58Updated: 07/20/2021 13:42
Changes: 03/15/2015 15:58 (51), 02/13/2017 10:10 (10), 07/20/2021 13:42 (4)
Complete: 🔍
Cache ID: 216:5D6:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.