CVE-2024-28134 Vulnerability Analysis & Exploit Details

CVE-2024-28134
Vulnerability Scoring

7.0
/10
High Risk

If left unpatched, CVE-2024-28134 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-28134 Details

Status: Analyzed

Last updated: 🕡 23 Jan 2025, 18:53 UTC
Originally published on: 🕓 14 May 2024, 16:16 UTC

Time between publication and last update: 254 days

CVSS Release: version 3

CVSS3 Source

info@cert.vde.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

CVE-2024-28134 Vulnerability Summary

CVE-2024-28134: An unauthenticated remote attacker can extract a session token with a MitM attack and gain web-based management access with the privileges of the currently logged in user due to cleartext transmission of sensitive information. No additional user interaction is required. The access is limited as only non-sensitive information can be obtained but the availability can be seriously affected. 

Assessing the Risk of CVE-2024-28134

Access Complexity Graph

The exploitability of CVE-2024-28134 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-28134

CVE-2024-28134 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-28134, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-28134, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2024-28134 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2024-28134 may cause minor changes to data without severely impacting its accuracy.
  • Availability: High
    CVE-2024-28134 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.065% (probability of exploit)

EPSS Percentile: 31.81% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 68.19% of others.

CVE-2024-28134 References

External References

CWE Common Weakness Enumeration

CWE-319

CAPEC Common Attack Pattern Enumeration and Classification

  • Session Sidejacking CAPEC-102 Session sidejacking takes advantage of an unencrypted communication channel between a victim and target system. The attacker sniffs traffic on a network looking for session tokens in unencrypted traffic. Once a session token is captured, the attacker performs malicious actions by using the stolen token with the targeted application to impersonate the victim. This attack is a specific method of session hijacking, which is exploiting a valid session token to gain unauthorized access to a target system or information. Other methods to perform a session hijacking are session fixation, cross-site scripting, or compromising a user or server machine and stealing the session token.
  • Interception CAPEC-117 An adversary monitors data streams to or from the target for information gathering purposes. This attack may be undertaken to solely gather sensitive information or to support a further attack against the target. This attack pattern can involve sniffing network traffic as well as other types of data streams (e.g. radio). The adversary can attempt to initiate the establishment of a data stream or passively observe the communications as they unfold. In all variants of this attack, the adversary is not the intended recipient of the data stream. In contrast to other means of gathering information (e.g., targeting data leaks), the adversary must actively position themself so as to observe explicit data channels (e.g. network traffic) and read the content. However, this attack differs from a Adversary-In-the-Middle (CAPEC-94) attack, as the adversary does not alter the content of the communications nor forward data to the intended recipient.
  • Harvesting Information via API Event Monitoring CAPEC-383 An adversary hosts an event within an application framework and then monitors the data exchanged during the course of the event for the purpose of harvesting any important data leaked during the transactions. One example could be harvesting lists of usernames or userIDs for the purpose of sending spam messages to those users. One example of this type of attack involves the adversary creating an event within the sub-application. Assume the adversary hosts a "virtual sale" of rare items. As other users enter the event, the attacker records via AiTM (CAPEC-94) proxy the user_ids and usernames of everyone who attends. The adversary would then be able to spam those users within the application using an automated script.
  • Signature Spoofing by Mixing Signed and Unsigned Content CAPEC-477 An attacker exploits the underlying complexity of a data structure that allows for both signed and unsigned content, to cause unsigned data to be processed as though it were signed data.
  • Sniff Application Code CAPEC-65 An adversary passively sniffs network communications and captures application code bound for an authorized client. Once obtained, they can use it as-is, or through reverse-engineering glean sensitive information or exploit the trust relationship between the client and server. Such code may belong to a dynamic update to the client, a patch being applied to a client component or any such interaction where the client is authorized to communicate with the server.

Vulnerable Configurations

  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3000:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3000:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3050:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3050:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3100:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.3.3:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.3.3:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3150:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3150:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-28134: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...
  • CVE-2025-1457 – The Element Pack Addons for Elementor – Free Templates and Widgets for Your WordPress Websites plugin for WordPress is vulnerable to Stored Cross-S...
  • CVE-2025-1093 – The AIHub theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the generate_image function in all ver...
  • CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...