VDB-86851 · OSVDB 60672 · GCVE-100-86851

First Class Client PROXYADDR 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.
5.3	$0-$5k	0.00

Summaryinfo

A vulnerability identified as critical has been detected in First Class Client. The affected element is an unknown function. This manipulation of the argument PROXYADDR causes memory corruption. There is not any exploit available.

Detailsinfo

A vulnerability classified as critical was found in First Class Client (affected version not known). Affected by this vulnerability is some unknown functionality. The manipulation of the argument PROXYADDR 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 bug was discovered 10/30/2003. The weakness was released 04/07/2004. Technical details of the vulnerability are known, but there is no available exploit.

After immediately, there has been an exploit disclosed. The vulnerability was handled as a non-public zero-day exploit for at least 160 days. During that time the estimated underground price was around $0-$5k.

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 vulnerability database at OSVDB (60672†). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

First Class

Name

Client

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: 🔍

Exploitinginfo

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

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Timelineinfo

10/30/2003 🔍
04/07/2004 +160 days 🔍
04/07/2004 +0 days 🔍
12/07/2009 +2070 days 🔍
05/09/2016 +2344 days 🔍
01/02/2019 +968 days 🔍

Sourcesinfo

Status: Not defined

GCVE (VulDB): GCVE-100-86851
OSVDB: 60672 - First Class Client Configuration File PROXYADDR Parameter Local Overflow

Entryinfo

Created: 05/09/2016 22:07
Updated: 01/02/2019 11:05
Changes: 05/09/2016 22:07 (38), 01/02/2019 11:05 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.