vciy

CVE-2021-39998

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

There is Vulnerability of APIs being concurrently called for multiple times in HwConnectivityExService a in smartphones

CVE-2021-399984 of 4 sources documented this
24

rank 24 = 0 + 19 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00697  ·  without this subject the record ranks 24

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.5, from NVD  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 24

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 19

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 24

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$21,300over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$21,300 = $4.99M incident cost x 0.6121449559255632 exposure x 0.00697 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00697EPSSNOT IN KEVas of 2026-09-20
Severity7.5 HIGHreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2022-01-08, 1619 days at 0.01, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running EMUI? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchharmonyos 2.0receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD7.5 HIGHreceipt
Exploit probability0.00697 · top 48% of all CVEsreceipt
Blast breadth3 products across 1 vendorderived
Assigned byhuaweireceipt
Recorded changes12 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productEMUI; Magic UI; HarmonyOSreceipt
Published rangeshuawei harmonyos < 2.0; huawei emui 11.0.0; huawei emui 11.0.1; huawei magic ui 4.0.0receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

There is Vulnerability of APIs being concurrently called for multiple times in HwConnectivityExService a in smartphones. Successful exploitation of this vulnerability may cause the system to crash and restart. receipt

NVD's analysis a second authority

severity
7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
affected versions
huawei harmonyos < 2.0; huawei emui 11.0.0; huawei emui 11.0.1; and 1 more, listed in full below

check it yourself device.harmonyos.com consumer.huawei.com receipt

Movement the material steps

8 Jan 20220.00624
7 Mar 20238.8e-4 · scoring model v2023.03.01
17 Mar 20250.00149 · scoring model v2025.03.14
15 Jun 20260.00697 · scoring model v2026.06.15
Show all 12 observations
8 Jan 20220.00624
4 Feb 20220.00885
7 Mar 20238.8e-4
8 Mar 20230.00088
20 Jun 20230.00097
31 Jul 20230.00101
13 Aug 20240.00102
22 Sep 20240.00116
17 Mar 20250.00149
29 Mar 20250.00214
30 Mar 20250.00149
15 Jun 20260.00697

12 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00697Published2022-01-07Index as of2026-06-15

The record had been public for 4 years, 5 months when this index was last written.

Published 2022-01-07 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

security-bulletins-202112-0000001183296718

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2021-39998.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.