CVE-2024-35143 Vulnerability Analysis & Exploit Details

CVE-2024-35143
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2024-35143 has severe implications, demanding immediate intervention.

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

Status: Analyzed

Last updated: 🕝 11 Sep 2024, 14:34 UTC
Originally published on: 🕐 04 Aug 2024, 13:15 UTC

Time between publication and last update: 38 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:H/I:H/A:N

CVE-2024-35143 Vulnerability Summary

CVE-2024-35143: IBM Planning Analytics Local 2.0 and 2.1 connects to a MongoDB server. MongoDB, a document-oriented database system, is listening on the remote port, and it is configured to allow connections without password authentication. A remote attacker can gain unauthorized access to the database. IBM X-Force ID: 292420.

Assessing the Risk of CVE-2024-35143

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2024-35143 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-35143, 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-35143, 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-35143 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-35143 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2024-35143 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.114% (probability of exploit)

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

CVE-2024-35143 References

External References

CWE Common Weakness Enumeration

CWE-306

CAPEC Common Attack Pattern Enumeration and Classification

  • Choosing Message Identifier CAPEC-12 This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.
  • Force the System to Reset Values CAPEC-166 An attacker forces the target into a previous state in order to leverage potential weaknesses in the target dependent upon a prior configuration or state-dependent factors. Even in cases where an attacker may not be able to directly control the configuration of the targeted application, they may be able to reset the configuration to a prior state since many applications implement reset functions.
  • Communication Channel Manipulation CAPEC-216 An adversary manipulates a setting or parameter on communications channel in order to compromise its security. This can result in information exposure, insertion/removal of information from the communications stream, and/or potentially system compromise.
  • Using Unpublished Interfaces or Functionality CAPEC-36 An adversary searches for and invokes interfaces or functionality that the target system designers did not intend to be publicly available. If interfaces fail to authenticate requests, the attacker may be able to invoke functionality they are not authorized for.
  • Cross Site Request Forgery CAPEC-62 An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.

Vulnerable Configurations

  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.54:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.54:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.55:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.55:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.56:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.56:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.57:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.57:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.58:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.58:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.59:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.59:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.60:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.60:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.61:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.61:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.62:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.62:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.63:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.63:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.64:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.64:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.65:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.65:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.66:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.66:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.67:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.67:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.68:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.68:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.69:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.69:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.70:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.70:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.71:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.71:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.72:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.72:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.73:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.73:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.74:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.74:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.75:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.75:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.76:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.76:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.77:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.77:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.78:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.78:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.79:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.79:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.80:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.80:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.81:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.81:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.82:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.82:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.83:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.83:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.84:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.84:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.85:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.85:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.86:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.86:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.87:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.87:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.88:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.88:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.89:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.89:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.90:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.90:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.91:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.91:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.92:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.92:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.93:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.93:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.94:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.94:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.95:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.95:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_workspace:2.0.96:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_workspace:2.0.96:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.9:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.9:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.0.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.0.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:planning_analytics_local:2.1.3:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:planning_analytics_local:2.1.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-35143: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...