CVE-2022-24262 Vulnerability Analysis & Exploit Details

CVE-2022-24262
Vulnerability Scoring

8.8
/10
Severe Risk

Cybersecurity professionals consider CVE-2022-24262 an immediate threat requiring urgent mitigation.

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: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-24262 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:50 UTC
Originally published on: 🕔 04 Feb 2022, 17:15 UTC

Time between publication and last update: 1020 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2022-24262 Vulnerability Summary

CVE-2022-24262: The config restore function of Voipmonitor GUI before v24.96 does not properly check files sent as restore archives, allowing remote attackers to execute arbitrary commands via a crafted file in the web root.

Assessing the Risk of CVE-2022-24262

Access Complexity Graph

The exploitability of CVE-2022-24262 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-2022-24262

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

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

CVE-2022-24262 References

External References

CWE Common Weakness Enumeration

CWE-434

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.

Vulnerable Configurations

  • cpe:2.3:a:voipmonitor:voipmonitor:-:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:-:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:22.20:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:22.20:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.0:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.0:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.1:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.1:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.2:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.2:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.3:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.3:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.4:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.4:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.5:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.5:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.6:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.6:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.7:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.7:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.8:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.8:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.9:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.9:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.10:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.10:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.11:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.11:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.12:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.12:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.13:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.13:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.14:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.14:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.15:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.15:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:23.16:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:23.16:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.0:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.0:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.1:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.1:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.2:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.2:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.3:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.3:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.4:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.4:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.5:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.5:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.6:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.6:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.7:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.7:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.8:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.8:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.9:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.9:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.10:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.10:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.11:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.11:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.12:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.12:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.13:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.13:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.14:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.14:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.15:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.15:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.16:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.16:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.17:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.17:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.18:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.18:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.19:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.19:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.20:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.20:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.21:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.21:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.22:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.22:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.23:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.23:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.24:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.24:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.25:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.25:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.26:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.26:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.27:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.27:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.28:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.28:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.29:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.29:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.31:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.31:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.32:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.32:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.33:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.33:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.34:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.34:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.35:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.35:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.36:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.36:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.37:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.37:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.38:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.38:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.39:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.39:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.40:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.40:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.41:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.41:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.42:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.42:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.43:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.43:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.44:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.44:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.45:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.45:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.46:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.46:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.47:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.47:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.48:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.48:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.50:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.50:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.51:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.51:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.52:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.52:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.53:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.53:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.54:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.54:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.55:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.55:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.56:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.56:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.57:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.57:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.58:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.58:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.59:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.59:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.60:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.60:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.61:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.61:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.62:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.62:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.63:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.63:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.64:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.64:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.65:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.65:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.66:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.66:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.67:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.67:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.68:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.68:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.69:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.69:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.70:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.70:*:*:*:*:*:*:*
  • cpe:2.3:a:voipmonitor:voipmonitor:24.71:*:*:*:*:*:*:*
    cpe:2.3:a:voipmonitor:voipmonitor:24.71:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-24262: 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-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
  • CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
  • CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
  • CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...
  • CVE-2025-3404 – The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the savePackage func...