Skip to content
Fencer Intel
low 3.8

CVE-2021-22799 json

A CWE-331: Insufficient Entropy vulnerability exists that could cause unintended connection from an internal network to an external network…

published 4y ago modified 4mo ago also EUVD-2021-9934

cvss
3.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

A CWE-331: Insufficient Entropy vulnerability exists that could cause unintended connection from an internal network to an external network when an attacker manages to decrypt the SESU proxy password from the registry. Affected Product: Schneider Electric Software Update, V2.3.0 through V2.5.1

Patch / fix

  • schneider-electric software_update 2.5.2

Is CVE-2021-22799 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-336-01 updated cvss 3.8

Schneider Electric SESU

  • Schneider Electric Software, LLC Schneider Electric Software Update >= 2.3.0, <= 2.5.1
    affected: mitigation “If SESU is installed (assuming SESU is configured as “managed product” inside the SESU application) it will indicate a security update is available. Click to download and install the new SESU version.” seupdate.schneider-electric.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

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

CVSS scores

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

Classification

Weakness

References

Sources

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.