CVE-2014-2358 json
Fox-IT DataDiode Appliance CSRF
published 2014-10-19 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2395
- cvss
- 4.3
- version 2.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
Multiple cross-site request forgery (CSRF) vulnerabilities in the administrative web interface in the proxy server on Fox-IT Fox DataDiode appliances before 1.7.2 allow remote attackers to hijack the authentication of administrators for requests that (1) create administrative users, (2) remove administrative users, or (3) change permissions.
Patch / fix
- Fox-IT DataDiode Appliance 1.7.2
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-14-269-02 updated cvss 4.3
Fox DataDiode Proxy Server CSRF Vulnerability
-
Fox-IT Fox DataDiode Appliance 1.7.1_and_belowaffected: mitigation “Fox-IT has released Version 1.7.2 of the Fox DataDiode Appliance that resolves the reported vulnerability”
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.57% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Fox-IT DataDiode Appliance
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
- cisa.gov /news-events/ics-advisories/icsa-14-269-02
-
ics-cert.us-cert.gov
/advisories/ICSA-14-269-02
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2014-2358
- NVD CVE-2014-2358
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.