What is the CVSS score of CVE-2019-15912?

CVE-2019-15912 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 1.3%.

Is there a public PoC exploit available for CVE-2019-15912?

Yes, a public proof-of-concept exploit is available for CVE-2019-15912. Prioritise patching immediately. EPSS: 1.3%.

Hg100 Firmware CVE-2019-15912

HIGH

Improper Input Validation (CWE-20)

2019-12-20 cve@mitre.org

Denial Of Service Hg100 Firmware Mw100 Firmware Ws 101 Firmware Ts 101 Firmware As 101 Firmware Ms 101 Firmware Dl 101 Firmware

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Dec 20, 2019 - 17:15 nvd

HIGH 7.5

DescriptionNVD

An issue was discovered on ASUS HG100, MW100, WS-101, TS-101, AS-101, MS-101, DL-101 devices using ZigBee PRO. Attackers can use the ZigBee trust center rejoin procedure to perform mutiple denial of service attacks.

AnalysisAI

An issue was discovered on ASUS HG100, MW100, WS-101, TS-101, AS-101, MS-101, DL-101 devices using ZigBee PRO. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-20. An issue was discovered on ASUS HG100, MW100, WS-101, TS-101, AS-101, MS-101, DL-101 devices using ZigBee PRO. Attackers can use the ZigBee trust center rejoin procedure to perform mutiple denial of service attacks. Affected products include: Asus Hg100 Firmware, Asus Mw100 Firmware, Asus Ws-101 Firmware, Asus Ts-101 Firmware, Asus As-101 Firmware.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.