| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Kphone up to 4.0.1. This vulnerability affects unknown code of the file sipclient.cpp. Performing a manipulation results in memory corruption. This vulnerability is identified as CVE-2004-1940. Additionally, an exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Kphone up to 4.0.1. This affects an unknown code of the file sipclient.cpp. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
sipclient.cpp in KPhone 4.0.1 and earlier allows remote attackers to cause a denial of service (crash) via a STUN response packet with a large attrLen value that causes an out-of-bounds read.
The weakness was released 12/31/2004 by STORM (Website). It is possible to read the advisory at wirlab.net. This vulnerability is uniquely identified as CVE-2004-1940 since 05/04/2005. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
A public exploit has been developed in Perl. The exploit is shared for download at securityfocus.com. It is declared as proof-of-concept.
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 (15874), Exploit-DB (24011), SecurityFocus (BID 10159†) and Vulnerability Center (SBV-4793†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
ISS Proventia IPS: 🔍
Timeline
04/08/2004 🔍04/08/2004 🔍
07/20/2004 🔍
12/31/2004 🔍
12/31/2004 🔍
05/04/2005 🔍
03/09/2015 🔍
01/11/2025 🔍
Sources
Advisory: wirlab.netResearcher: STORM
Status: Not defined
Confirmation: 🔍
CVE: CVE-2004-1940 (🔍)
GCVE (CVE): GCVE-0-2004-1940
GCVE (VulDB): GCVE-100-22971
X-Force: 15874
SecurityFocus: 10159 - KPhone Malformed STUN Packet Denial Of Service Vulnerability
Vulnerability Center: 4793 - DoS in Kphone SIP via Malformed STUN Packets, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/09/2015 15:52Updated: 01/11/2025 12:23
Changes: 03/09/2015 15:52 (59), 05/23/2019 12:03 (4), 01/11/2025 12:23 (21)
Complete: 🔍
Cache ID: 216:2C9:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.