CVE-2024-3913 Vulnerability Analysis & Exploit Details

CVE-2024-3913
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2024-3913 presents a notable risk, potentially requiring prompt mitigation.

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-3913 Details

Status: Undergoing Analysis

Last updated: 🕕 29 Jan 2025, 06:15 UTC
Originally published on: 🕐 13 Aug 2024, 13:15 UTC

Time between publication and last update: 168 days

CVSS Release: version 3

CVSS3 Source

info@cert.vde.com

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-3913 Vulnerability Summary

CVE-2024-3913: An unauthenticated remote attacker can use this vulnerability to change the device configuration due to a file writeable for short time after system startup.

Assessing the Risk of CVE-2024-3913

Access Complexity Graph

The exploitability of CVE-2024-3913 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-3913

CVE-2024-3913 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-3913, 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-3913, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2024-3913 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2024-3913 poses no threat to data integrity.
  • Availability: High
    CVE-2024-3913 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.067% (probability of exploit)

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

CVE-2024-3913 References

External References

CWE Common Weakness Enumeration

CWE-552

CAPEC Common Attack Pattern Enumeration and Classification

  • Collect Data from Common Resource Locations CAPEC-150 An adversary exploits well-known locations for resources for the purposes of undermining the security of the target. In many, if not most systems, files and resources are organized in a default tree structure. This can be useful for adversaries because they often know where to look for resources or files that are necessary for attacks. Even when the precise location of a targeted resource may not be known, naming conventions may indicate a small area of the target machine's file tree where the resources are typically located. For example, configuration files are normally stored in the /etc director on Unix systems. Adversaries can take advantage of this to commit other types of attacks.
  • Probe System Files CAPEC-639 An adversary obtains unauthorized information due to improperly protected files. If an application stores sensitive information in a file that is not protected by proper access control, then an adversary can access the file and search for sensitive information.

Vulnerable Configurations

  • 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:o:phoenixcontact:charx_sec-3150_firmware:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3150:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3150:-:*:*:*:*:*:*:*
  • 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:o:phoenixcontact:charx_sec-3100_firmware:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3100:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3100:-:*:*:*:*:*:*:*
  • 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:o:phoenixcontact:charx_sec-3050_firmware:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3050:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3050:-:*:*:*:*:*:*:*
  • 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:o:phoenixcontact:charx_sec-3000_firmware:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:h:phoenixcontact:charx_sec-3000:-:*:*:*:*:*:*:*
    cpe:2.3:h:phoenixcontact:charx_sec-3000:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-3913: 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-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...
  • CVE-2025-32953 – z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `...
  • CVE-2025-29058 – An issue in Qimou CMS v.3.34.0 allows a remote attacker to execute arbitrary code via the upgrade.php component.
  • CVE-2024-53591 – An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.