CVE-2022-25347 in the critical feed json
Delta Electronics DIAEnergie Path Traversal
published 4y ago modified 4mo ago also EUVD-2022-30023
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.4%
- EPSS 11.4% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Delta Electronics DIAEnergie (All versions prior to 1.8.02.004) is vulnerable to path traversal attacks, which may allow an attacker to write arbitrary files to locations on the file system.
Patch / fix
- Delta Electronics DIAEnergie 1.8.02.004
Is CVE-2022-25347 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-081-01 updated cvss 9.8
Delta Electronics DIAEnergie (Update C)
-
Delta Electronics DIAEnergie < 1.9affected: mitigation “Delta Electronics has fixed the reported vulnerabilities and recommends users upgrade to version 1.9 or later” downloadcenter.deltaww.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
- total
- Assessed
- last yr.
Exploit prediction
11.39% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Affected products
- Delta Electronics DIAEnergie
Classification
References
-
cisa.gov
/uscert/ics/advisories/icsa-22-081-01
mitigation, third-party-advisory, us-government-resource
Sources
- CVE List CVE-2022-25347
- NVD CVE-2022-25347
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.