CVE-2023-1620
Wago 750-8202 Firmware ≤ fw22
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-1620 is a medium-severity Improper Validation of Consistency within Input (CWE-1288) vulnerability in Wago 750-8202 Firmware. Its CVSS base score is 4.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-23852
Vulnerability Data
Multiple WAGO devices in multiple versions may allow an authenticated remote attacker with high privileges to DoS the device by sending a specifically crafted packet to the CODESYS V2 runtime.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V2.2.2V4.2.3V12.3.2
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require consistency validation for complex inputs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.8.25 mandates security requirements, checkpoints, secure coding, testing (incl. code scans) and developer training in the SDLC, which reaches a minority slice of consistency-validation defects when those practices are applied to input handling but leaves most instances (e.g. ad-hoc parsing, non-security requirements, post-SDLC changes) unaddressed.
A.8.26 explicitly requires identifying and addressing input validation and consistency-related requirements (items j, m, n, and resilience against injections/disruptions in d), which when implemented stops exploitation of consistency-validation flaws even if the code defect remains.
A.8.27 mandates security-by-design principles including data validation/sanitization, distrust-external-input, secure design reviews against attack patterns, and zero-trust verification of requests; this directly stops most consistency-validation flaws from being introduced or exploitable, with a bounded remainder in implementation gaps or non-applicable outsourced components.
Secure coding standards explicitly require validation of interrelated input fields to prevent CWE-1288.
Security testing can detect consistency flaws but does not prevent them at design time.