CVE-2024-23649 Vulnerability Analysis & Exploit Details

CVE-2024-23649
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2024-23649 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-23649 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:58 UTC
Originally published on: 🕕 24 Jan 2024, 18:15 UTC

Time between publication and last update: 301 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-23649 Vulnerability Summary

CVE-2024-23649: Lemmy is a link aggregator and forum for the fediverse. Starting in version 0.17.0 and prior to version 0.19.1, users can report private messages, even when they're neither sender nor recipient of the message. The API response to creating a private message report contains the private message itself, which means any user can just iterate over message ids to (loudly) obtain all private messages of an instance. A user with instance admin privileges can also abuse this if the private message is removed from the response, as they're able to see the resulting reports. Creating a private message report by POSTing to `/api/v3/private_message/report` does not validate whether the reporter is the recipient of the message. lemmy-ui does not allow the sender to report the message; the API method should likely be restricted to accessible to recipients only. The API response when creating a report contains the `private_message_report_view` with all the details of the report, including the private message that has been reported: Any authenticated user can obtain arbitrary (untargeted) private message contents. Privileges required depend on the instance configuration; when registrations are enabled without application system, the privileges required are practically none. When registration applications are required, privileges required could be considered low, but this assessment heavily varies by instance. Version 0.19.1 contains a patch for this issue. A workaround is available. If an update to a fixed Lemmy version is not immediately possible, the API route can be blocked in the reverse proxy. This will prevent anyone from reporting private messages, but it will also prevent exploitation before the update has been applied.

Assessing the Risk of CVE-2024-23649

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2024-23649 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-23649, 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-23649, 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-23649 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2024-23649 poses no threat to data integrity.
  • Availability: None
    CVE-2024-23649 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.064% (probability of exploit)

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

CVE-2024-23649 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:join-lemmy:lemmy:0.17.0:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.17.1:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.17.2:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.17.3:-:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.3:-:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.17.3:rc2:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.3:rc2:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.17.4:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.17.4:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.0:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.0:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.1:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.1:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.2:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.2:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.3:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.3:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.4:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.4:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.18.5:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.18.5:*:*:*:*:rust:*:*
  • cpe:2.3:a:join-lemmy:lemmy:0.19.0:*:*:*:*:rust:*:*
    cpe:2.3:a:join-lemmy:lemmy:0.19.0:*:*:*:*:rust:*:*

Protect Your Infrastructure against CVE-2024-23649: 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-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...