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

Summaryinfo

A vulnerability was found in LM_sensors. It has been rated as problematic. The affected element is an unknown function. This manipulation causes symlink. This vulnerability is handled as CVE-2005-2672. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in LM_sensors and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a symlink vulnerability. The CWE definition for the vulnerability is CWE-61. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files. As an impact it is known to affect integrity. The summary by CVE is:

pwmconfig in LM_sensors before 2.9.1 creates temporary files insecurely, which allows local users to overwrite arbitrary files via a symlink attack on the fancontrol temporary file.

The bug was discovered 08/22/2005. The weakness was released 08/23/2005 by Javier Fernandez-Sanguino Pena (Website). It is possible to read the advisory at vupen.com. This vulnerability is known as CVE-2005-2672 since 08/23/2005. The exploitation appears to be easy. Attacking locally is a requirement. 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. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 19572 (GLSA-200508-19 : lm_sensors: Insecure temporary file creation), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Gentoo Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117799 (CentOS Security Update for lm_sensors (CESA-2005:825)).

Upgrading to version 2.9.1 eliminates this vulnerability. A possible mitigation has been published 1 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (19572), SecurityFocus (BID 14624†), OSVDB (18905†), Secunia (SA16501†) and SecurityTracker (ID 1015180†). 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: 4.0
VulDB Meta Temp Score: 3.6

VulDB Base Score: 4.0
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Symlink
CWE: CWE-61 / CWE-59
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 19572
Nessus Name: GLSA-200508-19 : lm_sensors: Insecure temporary file creation
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 55336
OpenVAS Name: Debian Security Advisory DSA 814-1 (lm-sensors)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: LM_sensors 2.9.1

Timelineinfo

08/22/2005 🔍
08/22/2005 +0 days 🔍
08/22/2005 +0 days 🔍
08/23/2005 +1 days 🔍
08/23/2005 +0 days 🔍
08/23/2005 +0 days 🔍
08/23/2005 +0 days 🔍
08/30/2005 +7 days 🔍
09/06/2005 +7 days 🔍
09/12/2005 +6 days 🔍
11/10/2005 +59 days 🔍
03/11/2015 +3408 days 🔍
06/29/2025 +3763 days 🔍

Sourcesinfo

Advisory: vupen.com
Researcher: Javier Fernandez-Sanguino Pena
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2005-2672 (🔍)
GCVE (CVE): GCVE-0-2005-2672
GCVE (VulDB): GCVE-100-26131

OVAL: 🔍

SecurityFocus: 14624 - LM_sensors PWMConfig Insecure Temporary File Creation Vulnerability
Secunia: 16501 - LM Sensors Insecure Temporary File Creation Vulnerability, Less Critical
OSVDB: 18905 - LM_sensors - PWMConfig Insecure Temporary File Creation Issue
SecurityTracker: 1015180
Vulnerability Center: 9127 - LM_sensors pwmconfig Insecure Temporary File Creation, Medium
Vupen: ADV-2005-1492

Entryinfo

Created: 03/11/2015 23:39
Updated: 06/29/2025 22:14
Changes: 03/11/2015 23:39 (74), 06/09/2019 10:40 (13), 06/29/2025 22:14 (18)
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.

Might our Artificial Intelligence support you?

Check our Alexa App!