CVE-2024-1902 Vulnerability Analysis & Exploit Details

CVE-2024-1902
Vulnerability Scoring

7.5
/10
Very High Risk

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

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or 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-1902 Details

Status: Analyzed

Last updated: 🕑 10 Jan 2025, 14:29 UTC
Originally published on: 🕔 10 Apr 2024, 17:15 UTC

Time between publication and last update: 274 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2024-1902 Vulnerability Summary

CVE-2024-1902: lunary-ai/lunary is vulnerable to a session reuse attack, allowing a removed user to change the organization name without proper authorization. The vulnerability stems from the lack of validation to check if a user is still part of an organization before allowing them to make changes. An attacker can exploit this by using an old authorization token to send a PATCH request, modifying the organization's name even after being removed from the organization. This issue is due to incorrect synchronization and affects the orgs.patch route.

Assessing the Risk of CVE-2024-1902

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2024-1902 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

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-1902, 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-1902, 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-1902 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2024-1902 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2024-1902 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.054% (probability of exploit)

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

CVE-2024-1902 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:a:lunary:lunary:-:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:-:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.3:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.4:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.4:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.1.5:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.1.5:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:lunary:lunary:1.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:lunary:lunary:1.2.7:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-1902: 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.