CVE-2023-31240 Vulnerability Analysis & Exploit Details

CVE-2023-31240
Vulnerability Scoring

8.3
/10
Severe Risk

Cybersecurity professionals consider CVE-2023-31240 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: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-31240 Details

Status: Modified

Last updated: 🕕 09 Dec 2024, 18:15 UTC
Originally published on: 🕗 22 May 2023, 20:15 UTC

Time between publication and last update: 566 days

CVSS Release: version 3

CVSS3 Source

ics-cert@hq.dhs.gov

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-31240 Vulnerability Summary

CVE-2023-31240: Snap One OvrC Pro versions prior to 7.2 have their own locally running web server accessible both from the local network and remotely. OvrC cloud contains a hidden superuser account accessible through hard-coded credentials.

Assessing the Risk of CVE-2023-31240

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2023-31240 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-2023-31240, 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-31240, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2023-31240 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2023-31240 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2023-31240 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: 0.264% (probability of exploit)

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

CVE-2023-31240 References

External References

CWE Common Weakness Enumeration

CWE-1391

Vulnerable Configurations

  • cpe:2.3:a:snapone:orvc:-:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:-:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.2.0.5:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.2.0.5:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.2.1.7:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.2.1.7:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.3.0.4:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.3.0.4:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.3.0.6:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.3.0.6:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.4.0.3:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.4.0.3:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:6.4.0.9:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:6.4.0.9:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:7.0:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:7.0:*:*:*:*:pro:*:*
  • cpe:2.3:a:snapone:orvc:7.1.0:*:*:*:*:pro:*:*
    cpe:2.3:a:snapone:orvc:7.1.0:*:*:*:*:pro:*:*

Protect Your Infrastructure against CVE-2023-31240: 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...