There is an improper access control vulnerability in Huawei Share.

published 2019-11-29 6y ago modified 2026-06-17 4mo ago also EUVD-2019-14817

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits: 0; none known

There is an improper access control vulnerability in Huawei Share. The software does not properly restrict access to certain file from certain application. An attacker tricks the user into installing a malicious application then establishing a connect to the attacker through Huawei Share, successful exploit could cause information disclosure.

Patch / fix

fixed in 1

huawei p20_firmware emily-l29c_9.1.0.311\(c10e2r1p13t8\), emily-l29c_9.1.0.311\(c432e7r1p11t8\), emily-l29c_9.1.0.311\(c461e2r1p11t8\), emily-l29c_9.1.0.311\(c605e2r1p12t8\)

Is CVE-2019-5212 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N

Affected products

n/a P20

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource

References

huawei.com /en/psirt/security-advisories/huawei-sa-20191113-01-share-en
vendor-advisory

Sources

CVE List CVE-2019-5212
NVD CVE-2019-5212

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.