CVE-2022-46331 json
An unauthorized user could possibly delete any file on the system.
published 3y ago modified 4mo ago also EUVD-2022-49148
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
An unauthorized user could possibly delete any file on the system.
Patch / fix
- ge proficy_historian 2023
Is CVE-2022-46331 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-23-017-01 updated cvss 7.5
GE Digital Proficy Historian
-
GE Digital Proficy Historian >= v7.0affected: vendor fix, mitigation “Users can find out more about the vulnerabilities, how to obtain, and install the updates by visiting this notification document from GE Digital.” 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
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.54% chance of exploitation in the next 30 days, higher than 45% 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:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected products
- GE Digital Proficy Historian
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
digitalsupport.ge.com
/s/article/GE-Digital-Product-Security-Advisory-GED-23-01
permissions-required, vendor-advisory
-
cisa.gov
/uscert/ics/advisories/icsa-23-017-01
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-46331
- NVD CVE-2022-46331
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.