CVE-2022-21798 json
ICSA-22-053-02 GE Proficy CIMPLICITY-Cleartext
published 4y ago modified 4mo ago also EUVD-2022-26961
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 49%
- public exploits
- 0
- none known
Summary
The affected product is vulnerable due to cleartext transmission of credentials seen in the CIMPLICITY network, which can be easily spoofed and used to log in to make operational changes to the system.
Is CVE-2022-21798 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 FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-22-053-02 updated cvss 7.5
GE Proficy CIMPLICITY-Cleartext
-
General Electric (GE) Proficy CIMPLICITYaffected: mitigation “Users are advised to refer to the Secure Deployment Guide on how to configure communication encryption.” digitalsupport.ge.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
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.61% chance of exploitation in the next 30 days, higher than 49% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- General Electric Proficy CIMPLICITY
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-053-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-21798
- NVD CVE-2022-21798
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.