CVE-2024-3116 Vulnerability Analysis & Exploit Details

CVE-2024-3116
Vulnerability Scoring

7.4
/10
Very High Risk

Highly exploitable, CVE-2024-3116 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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-3116 Details

Status: Modified

Last updated: 🕕 13 Feb 2025, 18:18 UTC
Originally published on: 🕒 04 Apr 2024, 15:15 UTC

Time between publication and last update: 315 days

CVSS Release: version 3

CVSS3 Source

f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-3116 Vulnerability Summary

CVE-2024-3116: pgAdmin <= 8.4 is affected by a Remote Code Execution (RCE) vulnerability through the validate binary path API. This vulnerability allows attackers to execute arbitrary code on the server hosting PGAdmin, posing a severe risk to the database management system's integrity and the security of the underlying data.

Assessing the Risk of CVE-2024-3116

Access Complexity Graph

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

CVE-2024-3116 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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

  • Confidentiality: Low
    CVE-2024-3116 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2024-3116 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2024-3116 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 14.305% (probability of exploit)

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

CVE-2024-3116 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:pgadmin:pgadmin:-:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:-:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:-:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:-:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:rc1:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:rc1:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:beta1:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:beta1:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:beta2:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:beta2:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:beta3:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:beta3:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.0:beta4:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.0:beta4:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:1.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:1.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:2.0:-:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:2.0:-:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:2.0:rc1:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:2.0:rc1:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:2.0:rc2:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:2.0:rc2:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:2.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:2.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:3.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:3.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.7:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.7:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.8:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.8:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.9:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.9:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.10:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.10:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.11:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.11:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.12:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.12:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.13:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.13:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.14:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.14:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.15:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.15:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.16:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.16:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.17:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.17:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.18:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.18:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.19:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.19:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.20:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.20:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.21:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.21:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.22:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.22:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.23:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.23:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.24:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.24:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.25:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.25:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.26:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.26:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.27:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.27:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.28:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.28:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.29:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.29:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:4.30:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:4.30:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:5.7:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:5.7:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.7:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.7:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.8:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.8:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.9:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.9:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.10:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.10:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.11:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.11:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.12:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.12:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.13:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.13:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.14:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.14:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.15:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.15:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.16:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.16:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.17:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.17:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.18:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.18:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.20:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.20:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:6.21:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:6.21:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.0:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.0:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.1:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.1:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.2:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.2:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.3:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.3:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.4:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.4:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.5:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.5:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.6:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.6:*:*:*:*:postgresql:*:*
  • cpe:2.3:a:pgadmin:pgadmin:7.7:*:*:*:*:postgresql:*:*
    cpe:2.3:a:pgadmin:pgadmin:7.7:*:*:*:*:postgresql:*:*
  • cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:39:*:*:*:*:*:*:*

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