CVE-2025-8297 Vulnerability Analysis & Exploit Details

CVE-2025-8297
Vulnerability Scoring

7.2
/10
Very High Risk

Highly exploitable, CVE-2025-8297 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: 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-2025-8297 Details

Status: Analyzed

Last updated: 🕕 15 Aug 2025, 18:23 UTC
Originally published on: 🕒 12 Aug 2025, 15:15 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

3c1d8aa1-5a33-4ea4-8992-aadd6440af75

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2025-8297 Vulnerability Summary

CVE-2025-8297: Incomplete restriction of configuration in Ivanti Avalanche before version 6.4.8.8008 allows a remote authenticated attacker with admin privileges to achieve remote code execution

Assessing the Risk of CVE-2025-8297

Access Complexity Graph

The exploitability of CVE-2025-8297 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-2025-8297

The exploitability of CVE-2025-8297 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-2025-8297, 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-2025-8297, 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-2025-8297 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2025-8297 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2025-8297 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2025-8297 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:ivanti:avalanche:-:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:-:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:4.6:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:4.6:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:5.3:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:5.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:5.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.0:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.0:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.0:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.1:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.1.103.53:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.1.103.53:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.1.106.337:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.1.106.337:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.1.106.496:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.1.106.496:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2.0:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2.0:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2.0.602:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2.0.602:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2.2:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2.2:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.2.2.197:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.2.2.197:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.1:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.1:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.1.1507:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.1.1507:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:*:windows:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:*:windows:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.2:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.2.3490:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.2.3490:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.2.3490:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.2.3490:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.3:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.3:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.3.101:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.3.101:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.3.101:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.3.101:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.4:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.4:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.3.4.153:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.3.4.153:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.1:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.1:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.1.207:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.1.207:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.1.236:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.1.236:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.2:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.2:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.5:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.5:*:*:*:premise:*:*:*
  • cpe:2.3:a:ivanti:avalanche:6.4.6:*:*:*:premise:*:*:*
    cpe:2.3:a:ivanti:avalanche:6.4.6:*:*:*:premise:*:*:*

Protect Your Infrastructure against CVE-2025-8297: 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-10127 – Daikin Security Gateway is vulnerable to an authorization bypass through a user-controlled key vulnerability that could allow an attacker to bypa...
  • CVE-2025-9319 – A potential vulnerability was reported in the Lenovo Wallpaper Client that could allow arbitrary code execution under certain conditions.
  • CVE-2025-9214 – A missing authentication vulnerability was reported in some Lenovo printers that could allow a user to view limited device information or modify ne...
  • CVE-2025-9201 – A potential DLL hijacking vulnerability was discovered in Lenovo Browser during an internal security assessment that could allow a local user to ex...
  • CVE-2025-8557 – An internal product security audit of Lenovo XClarity Orchestrator (LXCO) discovered the below vulnerability: An attacker with access to a device ...