There is an out of bounds read vulnerability in eSE620X vESS V100R001C10SPC200, V100R001C20SPC200, V200R001C00SPC300.

published 2021-06-22 5y ago modified 2026-06-17 4mo ago also EUVD-2021-9511

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

There is an out of bounds read vulnerability in eSE620X vESS V100R001C10SPC200, V100R001C20SPC200, V200R001C00SPC300. A local attacker can exploit this vulnerability by sending specific message to the target device. Due to insufficient validation of internal message, successful exploit may cause the process and the service abnormal.

Is CVE-2021-22365 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.15% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	3.3	CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:N/I:N/A:P

Affected products

n/a eSE620X vESS

Classification

Weakness

CWE-125 Out-of-bounds Read

References

huawei.com /en/psirt/security-advisories/huawei-sa-20210526-02-outbounds-en
vendor-advisory

Sources

CVE List CVE-2021-22365
NVD CVE-2021-22365

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.