VDB-25757 · CVE-2005-2230 · BID 14235

elmo up to 1.3.2 R1

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

Summaryinfo

A vulnerability marked as problematic has been reported in elmo up to 1.3.2 R1. The affected element is an unknown function. The manipulation leads to an unknown weakness. This vulnerability is uniquely identified as CVE-2005-2230. No exploit exists.

Detailsinfo

A vulnerability was found in elmo up to 1.3.2 R1. It has been rated as problematic. Impacted is integrity. The summary by CVE is:

electronic mail operator (elmo) 1.3.2-r1 and earlier creates the elmostats temporary file insecurely which allows local users to overwrite arbitrary files.

The weakness was disclosed 07/12/2005 by Eric Romang (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2005-2230 since 07/12/2005. The exploitation is known to be easy. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

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 SecurityFocus (BID 14235†) and Secunia (SA15977†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

elmo

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 4.0
VulDB Temp Score: 4.0
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: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

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

Timelineinfo

07/12/2005 🔍
07/12/2005 +0 days 🔍
07/12/2005 +0 days 🔍
07/12/2005 +0 days 🔍
07/12/2005 +0 days 🔍
03/11/2015 +3529 days 🔍
07/10/2018 +1217 days 🔍

Sourcesinfo

Advisory: securityfocus.com⛔
Researcher: Eric Romang
Status: Not defined

CVE: CVE-2005-2230 (🔍)
GCVE (CVE): GCVE-0-2005-2230
GCVE (VulDB): GCVE-100-25757
SecurityFocus: 14235 - ELMO Insecure Temporary File Creation Vulnerability
Secunia: 15977 - Elmo "stats_dump()" Insecure Temporary File Creation, Less Critical

Entryinfo

Created: 03/11/2015 23:39
Updated: 07/10/2018 08:48
Changes: 03/11/2015 23:39 (45), 07/10/2018 08:48 (7)
Complete: 🔍
Cache ID: 216:17B:103

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