cve.bz

CVE-2018-7941 huawei: Improper Authentication

8.8 highEPSS 0.8%

High (8.8) in huawei. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei iBMC V200R002C60 have an authentication bypass vulnerability. A remote attacker with low privilege may craft specific messages to upload authentication certificate to the affected products. Due to improper validation of the upload authority, successful exploit may cause privilege elevation.

Severity

CVSS 3.0

8.8 high
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-7941 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-7941?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-7941?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-7941 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:ch121_v3_firmware100r001c00
huawei:ch121l_v3_firmware100r001c00
huawei:ch140_v3_firmware100r001c00
huawei:ch140l_v3_firmware100r001c00
huawei:ch220_v3_firmware100r001c00
huawei:ch222_v3_firmware100r001c00
huawei:ch242_v3_firmware100r001c00
huawei:rh1288_v3_firmware100r003c00
huawei:rh2288_v3_firmware100r003c00
huawei:rh2288h_v3_firmware100r003c00
huawei:xh310_v3_firmware100r003c00
huawei:xh321_v3_firmware100r003c00
huawei:xh620_v3_firmware100r003c00
huawei:ch121_v5_firmware100r001c00
huawei:ch121l_v5_firmware100r001c00
huawei:ch242_v5_firmware100r001c00
huawei:1288h_v5_firmware100r005c00
huawei:2288h_v5_firmware100r005c00
huawei:2488_v5_firmware100r005c00
huawei:xh321_v5_firmware100r005c00

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON