CVE-2022-28690 json
Horner Automation Cscape Csfont
published 4y ago modified 4mo ago also EUVD-2022-33132
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 61%
- public exploits
- 0
- none known
Summary
The affected product is vulnerable to an out-of-bounds write via uninitialized pointer, which may allow an attacker to execute arbitrary code.
Patch / fix
- Horner Automation Horner Automation Cscape Csfont Versions 9.90 SP5 (v9.90.196)
Is CVE-2022-28690 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-146-02 updated cvss 7.8
Horner Automation Cscape Csfont
-
Horner Automation Cscape Csfont <=9.90 SP5 (v9.90.196)affected: mitigation “Horner Automation recommends affected users update to the latest version of Cscape Csfont Version 9.90 SP6.” hornerautomation.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.95% chance of exploitation in the next 30 days, higher than 61% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Horner Automation Horner Automation Cscape Csfont
Classification
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-146-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-28690
- NVD CVE-2022-28690
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.