VDB-15821 · CVE-2000-0679 · EDB 20107

Client 1.10.8

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.
3.7	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Client 1.10.8. This vulnerability affects unknown code. The manipulation leads to an unknown weakness. This vulnerability is documented as CVE-2000-0679. Additionally, an exploit exists.

Detailsinfo

A vulnerability was found in Client 1.10.8. It has been rated as problematic. Impacted is integrity. The summary by CVE is:

the cvs 1.10.8 client trusts pathnames that are provided by the cvs server which allows the server to force the client to create arbitrary files.

The weakness was released 10/20/2000 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2000-0679. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are unknown but a public exploit is available.

The exploit is available at exploit-db.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 Exploit-DB (20107) and SecurityFocus (BID 1523†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Client

Version

1.10.8

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 3.7

VulDB Base Score: 4.0
VulDB Temp Score: 3.7
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: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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

07/28/2000 🔍
10/20/2000 +84 days 🔍
10/20/2000 +0 days 🔍
06/26/2014 +4997 days 🔍
01/20/2025 +3861 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Status: Not defined

CVE: CVE-2000-0679 (🔍)
GCVE (CVE): GCVE-0-2000-0679
GCVE (VulDB): GCVE-100-15821
SecurityFocus: 1523 - CVS Client Server-Instructed File Create Vulnerability

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

Entryinfo

Created: 06/26/2014 16:27
Updated: 01/20/2025 19:01
Changes: 06/26/2014 16:27 (34), 04/06/2019 00:24 (12), 01/20/2025 19:01 (27)
Complete: 🔍
Cache ID: 216::103

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