VDB-27187 · CVE-2005-3913 · SA17704

Vchs 2.4.6.2

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.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in Vchs 2.4.6.2. The affected element is an unknown function. This manipulation causes an unknown weakness. This vulnerability is tracked as CVE-2005-3913. No exploit exists.

Detailsinfo

A vulnerability was found in Vchs 2.4.6.2. It has been declared as problematic. As an impact it is known to affect integrity. The summary by CVE is:

Unspecified vulnerability in the domain alias management in Virtual Hosting Control System (VHCS) 2.4.6.2, related to "creating and deleting forwards for domain aliases," allows users to hijack the forwardings of other users.

The weakness was disclosed 11/23/2005 by Moritz Naumann (Website). It is possible to read the advisory at vhcs.net. This vulnerability is known as CVE-2005-3913 since 11/30/2005. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available.

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 OSVDB (21061†) and Secunia (SA17704†). The entry VDB-27177 is pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

11/23/2005 🔍
11/23/2005 +0 days 🔍
11/23/2005 +0 days 🔍
11/30/2005 +6 days 🔍
11/30/2005 +0 days 🔍
03/11/2015 +3388 days 🔍
07/13/2018 +1220 days 🔍

Sourcesinfo

Advisory: vhcs.net
Researcher: Moritz Naumann
Status: Not defined
Confirmation: 🔍

CVE: CVE-2005-3913 (🔍)
GCVE (CVE): GCVE-0-2005-3913
GCVE (VulDB): GCVE-100-27187
Secunia: 17704 - VHCS Multiple Vulnerabilities, Moderately Critical
OSVDB: 21061 - VHCS Domain Alias Management Unspecified Hijack
Vupen: ADV-2005-2534

See also: 🔍

Entryinfo

Created: 03/11/2015 23:39
Updated: 07/13/2018 08:31
Changes: 03/11/2015 23:39 (45), 07/13/2018 08:31 (8)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!