Phoenix Contact CHARX SEC-3150 up to 1.5.0 Service Restart cleanup

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

Summaryinfo

A vulnerability has been found in Phoenix Contact CHARX SEC-3000, CHARX SEC-3050, CHARX SEC-3100 and CHARX SEC-3150 up to 1.5.0 and classified as problematic. This issue affects some unknown processing of the component Service Restart. The manipulation leads to cleanup. This vulnerability is traded as CVE-2024-26005. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in Phoenix Contact CHARX SEC-3000, CHARX SEC-3050, CHARX SEC-3100 and CHARX SEC-3150 up to 1.5.0 and classified as problematic. This issue affects an unknown part of the component Service Restart. The manipulation with an unknown input leads to a cleanup vulnerability. Using CWE to declare the problem leads to CWE-459. The product does not properly "clean up" and remove temporary or supporting resources after they have been used. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An unauthenticated remote attacker can gain service level privileges through an incomplete cleanup during service restart after a DoS. 

The weakness was shared 03/12/2024 by Jack Dates as VDE-2024-011. The advisory is shared at cert.vde.com. The identification of this vulnerability is CVE-2024-26005 since 02/14/2024. 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.

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

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.2
VulDB Meta Temp Score: 5.1

VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 4.8
CNA Vector (CERT VDE): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Cleanup
CWE: CWE-459
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

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

02/14/2024 🔍
03/12/2024 +27 days 🔍
03/12/2024 +0 days 🔍
01/24/2025 +318 days 🔍

Sourcesinfo

Advisory: VDE-2024-011
Researcher: Jack Dates
Status: Not defined

CVE: CVE-2024-26005 (🔍)
GCVE (CVE): GCVE-0-2024-26005
GCVE (VulDB): GCVE-100-256469

Entryinfo

Created: 03/12/2024 10:35
Updated: 01/24/2025 05:10
Changes: 03/12/2024 10:35 (49), 01/24/2025 05:10 (15)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!