Picophone Internet Telephone up to 1.63 Logging memory corruption

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.9	$0-$5k	0.00

Summaryinfo

A vulnerability classified as critical has been found in Picophone Internet Telephone up to 1.63. This issue affects some unknown processing of the component Logging. This manipulation causes memory corruption. This vulnerability is registered as CVE-2004-1854. Furthermore, an exploit is available.

Detailsinfo

A vulnerability has been found in Picophone Internet Telephone up to 1.63 and classified as critical. Affected by this vulnerability is some unknown processing of the component Logging. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in the logging function in Picophone 1.63 and earlier allows remote attackers to execute arbitrary code via a large packet.

The weakness was published 03/24/2004 by Luigi Auriemma (Website). The advisory is shared at marc.theaimsgroup.com. This vulnerability is known as CVE-2004-1854 since 05/04/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.

It is possible to download the exploit 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 (15595), Exploit-DB (23876), SecurityFocus (BID 9969†), OSVDB (4550†) and Secunia (SA11209†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Picophone

Name

• Internet Telephone

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.44
• 1.45
• 1.46
• 1.47
• 1.48
• 1.49
• 1.50
• 1.51
• 1.52
• 1.53
• 1.54
• 1.55
• 1.56
• 1.57
• 1.58
• 1.59
• 1.60
• 1.61
• 1.62
• 1.63

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.9

VulDB Base Score: 7.3
VulDB Temp Score: 6.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Exploit-DB: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/24/2004 🔍
03/24/2004 +0 days 🔍
03/24/2004 +0 days 🔍
03/24/2004 +0 days 🔍
03/25/2004 +1 days 🔍
03/25/2004 +0 days 🔍
05/04/2005 +404 days 🔍
10/15/2014 +3451 days 🔍
10/09/2024 +3647 days 🔍

Sourcesinfo

Advisory: marc.theaimsgroup.com
Researcher: Luigi Auriemma
Status: Confirmed

CVE: CVE-2004-1854 (🔍)
GCVE (CVE): GCVE-0-2004-1854
GCVE (VulDB): GCVE-100-21685
X-Force: 15595 - PicoPhone logging function buffer overflow
SecurityFocus: 9969 - PicoPhone Internet Phone Remote Buffer Overflow Vulnerability
Secunia: 11209 - PicoPhone Logging Functionality Buffer Overflow Vulnerability, Highly Critical
OSVDB: 4550 - PicoPhone Logging Functionality Remote Overflow
SecurityTracker: 1009551 - PicoPhone Buffer Overflow Lets Remote Users Execute Arbitrary Code

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 10/15/2014 17:03
Updated: 10/09/2024 04:19
Changes: 10/15/2014 17:03 (62), 07/05/2017 09:21 (7), 10/09/2024 04:19 (17)
Complete: 🔍
Cache ID: 216:CF9:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

Do you want to use VulDB in your project?

Use the official API to access entries easily!