CVE-2014-9693 Vulnerability Analysis & Exploit Details

CVE-2014-9693
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2014-9693 has severe implications, demanding immediate intervention.

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-2014-9693 Details

Status: Modified

Last updated: 🕑 21 Nov 2024, 02:21 UTC
Originally published on: 🕣 02 Apr 2017, 20:59 UTC

Time between publication and last update: 2789 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:H/I:H/A:H

CVE-2014-9693 Vulnerability Summary

CVE-2014-9693: Huawei Tecal RH1288 V2 V100R002C00SPC107 and earlier versions, Tecal RH2265 V2 V100R002C00, Tecal RH2285 V2 V100R002C00SPC115 and earlier versions, Tecal RH2265 V2 V100R002C00, Tecal RH2285H V2 V100R002C00SPC111 and earlier versions, Tecal RH2268 V2 V100R002C00, Tecal RH2288 V2 V100R002C00SPC117 and earlier versions, Tecal RH2288H V2 V100R002C00SPC115 and earlier versions, Tecal RH2485 V2 V100R002C00SPC502 and earlier versions, Tecal RH5885 V2 V100R001C02SPC109 and earlier versions, Tecal RH5885 V3 V100R003C01SPC102 and earlier versions, Tecal RH5885H V3 V100R003C00SPC102 and earlier versions, Tecal XH310 V2 V100R001C00SPC110 and earlier versions, Tecal XH311 V2 V100R001C00SPC110 and earlier versions, Tecal XH320 V2 V100R001C00SPC110 and earlier versions, Tecal XH621 V2 V100R001C00SPC106 and earlier versions, Tecal DH310 V2 V100R001C00SPC110 and earlier versions, Tecal DH320 V2 V100R001C00SPC106 and earlier versions, Tecal DH620 V2 V100R001C00SPC106 and earlier versions, Tecal DH621 V2 V100R001C00SPC107 and earlier versions, Tecal DH628 V2 V100R001C00SPC107 and earlier versions, Tecal BH620 V2 V100R002C00SPC107 and earlier versions, Tecal BH621 V2 V100R002C00SPC106 and earlier versions, Tecal BH622 V2 V100R002C00SPC110 and earlier versions, Tecal BH640 V2 V100R002C00SPC108 and earlier versions, Tecal CH121 V100R001C00SPC180 and earlier versions, Tecal CH140 V100R001C00SPC110 and earlier versions, Tecal CH220 V100R001C00SPC180 and earlier versions, Tecal CH221 V100R001C00SPC180 and earlier versions, Tecal CH222 V100R002C00SPC180 and earlier versions, Tecal CH240 V100R001C00SPC180 and earlier versions, Tecal CH242 V100R001C00SPC180 and earlier versions, Tecal CH242 V3 V100R001C00SPC110 and earlier versions could allow attackers to execute arbitrary code or restart the system via crafted DNS packets.

Assessing the Risk of CVE-2014-9693

Access Complexity Graph

The exploitability of CVE-2014-9693 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-2014-9693

With low attack complexity and no required privileges, CVE-2014-9693 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-2014-9693, 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-2014-9693, 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-2014-9693 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2014-9693 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2014-9693 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.396% (probability of exploit)

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

CVE-2014-9693 References

External References

CWE Common Weakness Enumeration

CWE-19

Vulnerable Configurations

  • cpe:2.3:o:huawei:tecal_rh1288_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh1288_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh1288_v2_firmware:v100r002c00spc107:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh1288_v2_firmware:v100r002c00spc107:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh1288_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh1288_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2265_v2_firmware:v100r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2265_v2_firmware:v100r002c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2265_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2265_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2285_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2285_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2285_v2_firmware:v100r002c00spc115:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2285_v2_firmware:v100r002c00spc115:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2285_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2285_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2285h_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2285h_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2285h_v2_firmware:v100r002c00spc111:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2285h_v2_firmware:v100r002c00spc111:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2285h_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2285h_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2268_v2_firmware:v100r002c00:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2268_v2_firmware:v100r002c00:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2268_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2268_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2288_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2288_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2288_v2_firmware:v100r002c00spc117:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2288_v2_firmware:v100r002c00spc117:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2288_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2288_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2288h_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2288h_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2288h_v2_firmware:v100r002c00spc115:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2288h_v2_firmware:v100r002c00spc115:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2288h_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2288h_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2485_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2485_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh2485_v2_firmware:v100r002c00spc502:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh2485_v2_firmware:v100r002c00spc502:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh2485_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh2485_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885_v2_firmware:v100r001c02spc109:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885_v2_firmware:v100r001c02spc109:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh5885_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh5885_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885_v3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885_v3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885_v3_firmware:v100r003c01spc102:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885_v3_firmware:v100r003c01spc102:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh5885_v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh5885_v3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885h_v3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885h_v3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_rh5885h_v3_firmware:v100r003c00spc102:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_rh5885h_v3_firmware:v100r003c00spc102:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_rh5885h_v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_rh5885h_v3:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh310_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh310_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh310_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh310_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_xh310_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_xh310_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh311_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh311_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh311_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh311_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_xh311_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_xh311_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh320_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh320_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh320_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh320_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_xh320_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_xh320_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh621_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh621_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_xh621_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_xh621_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_xh621_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_xh621_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh310_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh310_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh310_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh310_v2_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_dh310_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_dh310_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh320_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh320_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh320_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh320_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_dh320_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_dh320_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh620_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh620_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh620_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh620_v2_firmware:v100r001c00spc106:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_dh620_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_dh620_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh621_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh621_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh621_v2_firmware:v100r001c00spc107:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh621_v2_firmware:v100r001c00spc107:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_dh621_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_dh621_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh628_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh628_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_dh628_v2_firmware:v100r001c00spc107:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_dh628_v2_firmware:v100r001c00spc107:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_dh628_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_dh628_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh620_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh620_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh620_v2_firmware:v100r002c00spc107:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh620_v2_firmware:v100r002c00spc107:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_bh620_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_bh620_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh621_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh621_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh621_v2_firmware:v100r002c00spc106:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh621_v2_firmware:v100r002c00spc106:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_bh621_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_bh621_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh622_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh622_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh622_v2_firmware:v100r002c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh622_v2_firmware:v100r002c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_bh622_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_bh622_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh640_v2_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh640_v2_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_bh640_v2_firmware:v100r002c00spc108:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_bh640_v2_firmware:v100r002c00spc108:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_bh640_v2:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_bh640_v2:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch121_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch121_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch121_firmware:v100r001c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch121_firmware:v100r001c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch121:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch121:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch140_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch140_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch140_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch140_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch140:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch140:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch220_firmware:v100r001c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch220_firmware:v100r001c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch220:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch221_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch221_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch221_firmware:v100r001c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch221_firmware:v100r001c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch221:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch221:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch222_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch222_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch222_firmware:v100r002c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch222_firmware:v100r002c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch222:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch222:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch240_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch240_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch240_firmware:v100r001c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch240_firmware:v100r001c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch240:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch240:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch242_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch242_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch242_firmware:v100r001c00spc180:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch242_firmware:v100r001c00spc180:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch242:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch242:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch242_v3_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch242_v3_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:o:huawei:tecal_ch242_v3_firmware:v100r001c00spc110:*:*:*:*:*:*:*
    cpe:2.3:o:huawei:tecal_ch242_v3_firmware:v100r001c00spc110:*:*:*:*:*:*:*
  • cpe:2.3:h:huawei:tecal_ch242_v3:-:*:*:*:*:*:*:*
    cpe:2.3:h:huawei:tecal_ch242_v3:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2014-9693: 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...