IPTel SIP Express Router up to 0.8.9 Session Initiation Protocol INVITE Message memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in IPTel SIP Express Router up to 0.8.9 and classified as critical. This vulnerability affects unknown code of the component Session Initiation Protocol. The manipulation as part of INVITE Message leads to memory corruption. This vulnerability is documented as CVE-2003-1113. There is not any exploit available.
Details
A vulnerability was found in IPTel SIP Express Router up to 0.8.9 (Router Operating System) and classified as critical. This issue affects an unknown part of the component Session Initiation Protocol. The manipulation as part of a INVITE Message leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
The Session Initiation Protocol (SIP) implementation in IPTel SIP Express Router 0.8.9 and earlier allows remote attackers to cause a denial of service and possibly execute arbitrary code via crafted INVITE messages, as demonstrated by the OUSPG PROTOS c07-sip test suite.
The weakness was released 12/31/2003 with Oulu University Secure Programming Group as confirmed advisory (CERT.org). The advisory is shared at kb.cert.org. The identification of this vulnerability is CVE-2003-1113 since 03/11/2005. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly 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 (11379) and SecurityFocus (BID 6904†). Entries connected to this vulnerability are available at VDB-21096, VDB-21097, VDB-21098 and VDB-21099. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
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: Memory corruptionCWE: CWE-119
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
02/21/2003 🔍12/31/2003 🔍
12/31/2003 🔍
03/11/2005 🔍
08/22/2014 🔍
11/19/2024 🔍
Sources
Advisory: kb.cert.orgOrganization: Oulu University Secure Programming Group
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2003-1113 (🔍)
GCVE (CVE): GCVE-0-2003-1113
GCVE (VulDB): GCVE-100-21101
CERT: 🔍
X-Force: 11379
SecurityFocus: 6904 - Multiple Vendor Session Initiation Protocol Vulnerabilities
See also: 🔍
Entry
Created: 08/22/2014 13:21Updated: 11/19/2024 09:15
Changes: 08/22/2014 13:21 (51), 07/04/2017 08:03 (6), 11/19/2024 09:15 (17)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.