MediumCVE-2017-15333

Huawei S5700 Firmware: security vulnerability (CVE-2017-15333)

Published 15.02.2018Sources: CVE.org

What is affected, what to do

XML parser in Huawei S12700 V200R005C00,S1700 V200R009C00, V200R010C00,S3700 V100R006C03, V100R006C05,S5700 V200R001C00, V200R002C00, V200R003C00, V200R003C02, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,S6700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R005C02, V200R008C00, V200R009C00, V200R010C00,S7700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,S9700 V200R001C00, V200R002C00, V200R003C00, V200R005C00, V200R006C00, V200R007C00, V200R008C00, V200R009C00, V200R010C00,eCNS210_TD V100R004C10, V100R004C10SPC003, V100R004C10SPC100, V100R004C10SPC101, V100R004C10SPC102, V100R004C10SPC200, V100R004C10SPC221, V100R004C10SPC400 has a DOS vulnerability. An attacker may craft specific XML files to the affected products.

The available sources name no fixed version. Check the vendor guidance in the references below.

Affected: Huawei Technologies S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD eq S12700 V200R005C00,S1700 V200R009C00, V200R010C00,S3700 V100R006C03, V100R006C05,S5700 V200R001C00, V200R002C00, V200R003C00, V2..S12700 V200R005C00,S1700 V200R009C00, V200R010C00,S3700 V100R006C03, V100R006C05,S5700 V200R001C00, V200R002C00, V200R003C00, V2

Not sure whether and how you are affected? Ask a question about this vulnerability

Metrics

4.7

Priority

XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

Source: NVD, CVSS v3

4.7

CVSS v3

Severity Medium on the scale from 0 to 10.

Source: CVE.org

0.5 %

EPSS score

Low — model estimates < 1% exploitation likelihood.

Source: FIRST EPSS, percentile 41.8

Show all metrics

Severity: Medium
Priority (0–325) The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first? Read in glossary: 37.46 Methodology
Exploit maturity An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack. Read in glossary: no public PoC known
XIEM Effective CVSS XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command. Read in glossary: 4.7 Methodology
CVSS v3 CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions. Read in glossary: 4.7
EPSS score The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“. Read in glossary: 0.5 %; Low — model estimates < 1% exploitation likelihood.
EPSS percentile The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking. Read in glossary: 41.8; High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching. Read in glossary: —
Published: 15.02.2018

Detection rules

No NEOSEC detection rule is available for this vulnerability yet.

Classification under NIS2 and CRA

Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

NIS2 NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management. Read in glossary: Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
CRA The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates. Read in glossary: From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001 ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security. Read in glossary: Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

Description

Source: NVD (NIST), cvelistv5

Affected products

The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

Affected products
		Affected versions	Fixed in
Huawei Technologies Co., Ltd.	S12700, S1700,S3700,S5700,S6700,S7700, S9700, eCNS210_TD	`S12700 V200R005C00,S1700 V200R009C00, V200R010C00,S3700 V100R006C03, V100R006C05,S5700 V200R001C00, V200R002C00, V200R003C00, V2`	—

Vendors and products

Affected operating systems

Affected operating systems

Other	huawei	ecns210_td_firmware	`v100r004c10`
Other	huawei	ecns210_td_firmware	`v100r004c10spc003`
Other	huawei	ecns210_td_firmware	`v100r004c10spc100`
Other	huawei	ecns210_td_firmware	`v100r004c10spc101`
Other	huawei	ecns210_td_firmware	`v100r004c10spc102`
Other	huawei	ecns210_td_firmware	`v100r004c10spc200`
Other	huawei	ecns210_td_firmware	`v100r004c10spc221`
Other	huawei	ecns210_td_firmware	`v100r004c10spc400`
Other	huawei	s12700_firmware	`v200r005c00`
Other	huawei	s1700_firmware	`v200r009c00`
Other	huawei	s1700_firmware	`v200r010c00`
Other	huawei	s5700_firmware	`v200r001c00`
Other	huawei	s5700_firmware	`v200r002c00`
Other	huawei	s5700_firmware	`v200r003c00`
Other	huawei	s5700_firmware	`v200r003c02`
Other	huawei	s5700_firmware	`v200r005c00`
Other	huawei	s5700_firmware	`v200r006c00`
Other	huawei	s5700_firmware	`v200r007c00`
Other	huawei	s5700_firmware	`v200r008c00`
Other	huawei	s5700_firmware	`v200r009c00`
Other	huawei	s5700_firmware	`v200r010c00`
Other	huawei	s6700_firmware	`v200r001c00`
Other	huawei	s6700_firmware	`v200r002c00`
Other	huawei	s6700_firmware	`v200r003c00`

References & sources

huawei.comen/psirt/security-advisories/huawei-sa-20171201-01-xml-enx_refsource_CONFIRM, Vendor advisory

Embed badge

Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

<a href="https://intel.neosec.eu/en/cve/CVE-2017-15333"><img src="https://intel.neosec.eu/badge/cve/CVE-2017-15333.svg?lang=en" alt="CVE-2017-15333 – NEOSEC Intel" height="20"></a>