CVE-2023-3264 Vulnerability Analysis & Exploit Details

CVE-2023-3264
Vulnerability Scoring

6.7
/10
High Risk

If left unpatched, CVE-2023-3264 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: High
    High-level 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-2023-3264 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:16 UTC
Originally published on: 🕔 14 Aug 2023, 05:15 UTC

Time between publication and last update: 465 days

CVSS Release: version 3

CVSS3 Source

trellixpsirt@trellix.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-3264 Vulnerability Summary

CVE-2023-3264: The Dataprobe iBoot PDU running firmware version 1.43.03312023 or earlier uses hard-coded credentials for all interactions with the internal Postgres database. A malicious agent with the ability to execute operating system commands on the device can leverage this vulnerability to read, modify, or delete arbitrary database records.

Assessing the Risk of CVE-2023-3264

Access Complexity Graph

The exploitability of CVE-2023-3264 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-2023-3264

The exploitability of CVE-2023-3264 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

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

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

CVE-2023-3264 References

External References

CWE Common Weakness Enumeration

CWE-798

CAPEC Common Attack Pattern Enumeration and Classification

  • Read Sensitive Constants Within an Executable CAPEC-191 An adversary engages in activities to discover any sensitive constants present within the compiled code of an executable. These constants may include literal ASCII strings within the file itself, or possibly strings hard-coded into particular routines that can be revealed by code refactoring methods including static and dynamic analysis.
  • Try Common or Default Usernames and Passwords CAPEC-70 An adversary may try certain common or default usernames and passwords to gain access into the system and perform unauthorized actions. An adversary may try an intelligent brute force using empty passwords, known vendor default credentials, as well as a dictionary of common usernames and passwords. Many vendor products come preconfigured with default (and thus well-known) usernames and passwords that should be deleted prior to usage in a production environment. It is a common mistake to forget to remove these default login credentials. Another problem is that users would pick very simple (common) passwords (e.g. "secret" or "password") that make it easier for the attacker to gain access to the system compared to using a brute force attack or even a dictionary attack using a full dictionary.

Vulnerable Configurations

  • cpe:2.3:o:dataprobe:iboot-pdu4a-c10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-c10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4a-c10:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4a-c10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-c20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-c20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4a-c20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4a-c20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4a-n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4a-n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4a-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4a-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4a-n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4a-n20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4-c20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4-c20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4-c20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4-c20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4-n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4-n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4-n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4-n20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-c10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-c10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4sa-c10:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4sa-c10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-c20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-c20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4sa-c20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4sa-c20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4sa-n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4sa-n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu4sa-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu4sa-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu4sa-n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu4sa-n20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2c10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2c10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2c10_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2c10_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-2c10:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-2c10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2c20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2c20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2c20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2c20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-2c20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-2c20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-2n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-2n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-2n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-2n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-2n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-2n20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-c10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-c10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-c10:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-c10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-c20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-c20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-c20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-c20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-c20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8a-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8a-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8a-n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8a-n20:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-2n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-2n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-2n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-2n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8sa-2n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8sa-2n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-c10_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-c10_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-c10_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8sa-c10:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8sa-c10:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-n15_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-n15_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-n15_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8sa-n15:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8sa-n15:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-n20_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-n20_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:dataprobe:iboot-pdu8sa-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
    cpe:2.3:o:dataprobe:iboot-pdu8sa-n20_firmware:1.42.06162022:*:*:*:*:*:*:*
  • cpe:2.3:h:dataprobe:iboot-pdu8sa-n20:-:*:*:*:*:*:*:*
    cpe:2.3:h:dataprobe:iboot-pdu8sa-n20:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-3264: 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-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
  • CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
  • CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
  • CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...
  • CVE-2025-2118 – A vulnerability was found in Quantico Tecnologia PRMV 6.48. It has been classified as critical. This affects an unknown part of the file /admin/log...