CVE-2015-2800 Vulnerability Analysis & Exploit Details

CVE-2015-2800
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2015-2800 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: None
    No 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-2015-2800 Details

Status: Modified

Last updated: 🕑 21 Nov 2024, 02:28 UTC
Originally published on: 🕓 08 Jun 2017, 16:29 UTC

Time between publication and last update: 2722 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2015-2800 Vulnerability Summary

CVE-2015-2800: The user authentication module in Huawei Campus switches S5700, S5300, S6300, and S6700 with software before V200R001SPH012 and S7700, S9300, and S9700 with software before V200R001SPH015 allows remote attackers to cause a denial of service (device restart) via vectors involving authentication, which trigger an array access violation.

Assessing the Risk of CVE-2015-2800

Access Complexity Graph

The exploitability of CVE-2015-2800 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-2015-2800

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

  • Confidentiality: None
    CVE-2015-2800 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2015-2800 poses no threat to data integrity.
  • Availability: High
    CVE-2015-2800 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.164% (probability of exploit)

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

CVE-2015-2800 References

External References

CWE Common Weakness Enumeration

CWE-287

CAPEC Common Attack Pattern Enumeration and Classification

  • Authentication Abuse CAPEC-114 An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.
  • Authentication Bypass CAPEC-115 An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.
  • Identity Spoofing CAPEC-151 Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.
  • Fake the Source of Data CAPEC-194 An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.
  • Exploiting Trust in Client CAPEC-22 An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Obtain Sensitive Data CAPEC-57 This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.
  • Session Hijacking CAPEC-593 This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.
  • Token Impersonation CAPEC-633 An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.
  • Upload a Web Shell to a Web Server CAPEC-650 By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.
  • Adversary in the Middle (AiTM) CAPEC-94 An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.

Vulnerable Configurations

  • cpe:2.3:o:huawei:s5700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v100r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v100r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v100r006c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v100r006c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s5700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s5700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r005c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r005c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006c01:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006c01:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006c01spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006c01spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v100r006c03:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v100r006c03:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s5300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s5300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s5300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s5300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v100r006c01spc100:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v100r006c01spc100:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v100r006c03:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v100r006c03:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s6300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s6300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:2r11c10:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:2r11c10:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s6700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s6700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s6700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s6700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v100r002:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v100r002:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v100r003:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v100r003:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v100r003c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v100r003c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s7700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s7700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s7700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s7700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r002:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r002:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r002c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r003:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r003:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r003c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r003c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r006c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r006c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r006c00spc500:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r006c00spc500:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v100r006c00spc800:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9300_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s9300:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s9300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v100r006:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v100r006:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r001:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r001:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r001c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r001c00:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:s9700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:s9700_firmware:v200r001c00spc300:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:campus_s9700:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:campus_s9700:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2015-2800: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...