CVE-2024-35057 Vulnerability Analysis & Exploit Details

CVE-2024-35057
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2024-35057 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • 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-35057 Details

Status: Analyzed

Last updated: 🕑 03 Jun 2025, 14:15 UTC
Originally published on: 🕕 21 May 2024, 18:15 UTC

Time between publication and last update: 377 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-35057 Vulnerability Summary

CVE-2024-35057: An issue in NASA AIT-Core v2.5.2 allows attackers to execute arbitrary code via a crafted packet.

Assessing the Risk of CVE-2024-35057

Access Complexity Graph

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

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

  • Confidentiality: High
    Exploiting CVE-2024-35057 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-35057 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-35057 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.043% (probability of exploit)

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

CVE-2024-35057 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:a:nasa:ait_core:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.19.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.19.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.19.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.19.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.20.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.20.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.21.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.21.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.22.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.22.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.23.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.24.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.25.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.25.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.26.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.26.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.26.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.26.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.26.2:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.26.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.27.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.27.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.27.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.27.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.28.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.28.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.29.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.29.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.30.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.30.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.31.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.31.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.31.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.31.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.32.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.32.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.33.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.33.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.33.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.33.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.33.2:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.33.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.34.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.34.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.35.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.35.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.36.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.36.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:0.37.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:0.37.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.0:rc1_dev0:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.0:rc1_dev0:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.3.6:rc1:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.3.6:rc1:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:nasa:ait_core:2.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:nasa:ait_core:2.5.2:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-35057: 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-9558 – There is a potential OOB Write vulnerability in the gen_prov_start function in pb_adv.c. The full length of the received data is copied into the li...
  • CVE-2025-9557 – ‭An out-of-bound write can lead to an arbitrary code execution. Even on devices with some form of memory protection, this can still lead to‬ ‭a cra...
  • CVE-2025-59820 – In KDE Krita before 5.2.13, loading a manipulated TGA file could result in a heap-based buffer overflow in plugins/impex/tga/kis_tga_import.cpp (ak...
  • CVE-2025-55174 – In KDE Skanpage before 25.08.0, an attempt at file overwrite can result in the contents of the new file at the beginning followed by the partial co...
  • CVE-2025-12061 – The TAX SERVICE Electronic HDM WordPress plugin before 1.2.1 does not authorization and CSRF checks in an AJAX action, allowing unauthenticated use...