MediumCVE-2023-37552

    CODESYS Improper Input Validation in CmpAppBP (CVE-2023-37552)

    Published Sources: Schneider Electric, CVE.org

    What is affected, what to do

    In multiple versions of multiple Codesys products, after successful authentication as a user, specific crafted network communication requests with inconsistent content can cause the CmpAppBP component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37553, CVE-2023-37554, CVE-2023-37555 and CVE-2023-37556.

    Update CODESYS Control for BeagleBone SL to version 4.10.0.0, CODESYS Control for emPC-A/iMX6 SL to version 4.10.0.0, CODESYS Control for IOT2000 SL to version 4.10.0.0.

    Affected
    • CODESYS Control for BeagleBone SL lt *..4.10.0.0
    • CODESYS Control for emPC-A/iMX6 SL lt *..4.10.0.0
    • CODESYS Control for IOT2000 SL lt *..4.10.0.0
    • CODESYS Control for Linux SL lt *..4.10.0.0
    • CODESYS Control for PFC100 SL lt *..4.10.0.0
    • CODESYS Control for PFC200 SL lt *..4.10.0.0
    • CODESYS Control for PLCnext SL lt *..4.10.0.0
    • CODESYS Control for Raspberry Pi SL lt *..4.10.0.0
    • CODESYS Control for WAGO Touch Panels 600 SL lt *..4.10.0.0
    • CODESYS Control RTE (SL) lt *..3.5.19.20
    • CODESYS Control Rte Sl (for Beckhoff Cx) lt *..3.5.19.20
    • CODESYS Control Runtime System Toolkit lt *..3.5.19.20
    • CODESYS Control Win (SL) lt *..3.5.19.20
    • CODESYS Development System lt *..3.5.19.20
    • Codesys Hmi lt *..3.5.19.20
    • CODESYS Safety SIL2 lt *..3.5.19.20
    Fixed in
    • CODESYS Control for BeagleBone SL 4.10.0.0
    • CODESYS Control for emPC-A/iMX6 SL 4.10.0.0
    • CODESYS Control for IOT2000 SL 4.10.0.0
    • CODESYS Control for Linux SL 4.10.0.0
    • CODESYS Control for PFC100 SL 4.10.0.0
    • CODESYS Control for PFC200 SL 4.10.0.0
    • CODESYS Control for PLCnext SL 4.10.0.0
    • CODESYS Control for Raspberry Pi SL 4.10.0.0
    • CODESYS Control for WAGO Touch Panels 600 SL 4.10.0.0
    • CODESYS Control RTE (SL) 3.5.19.20
    • CODESYS Control Rte Sl (for Beckhoff Cx) 3.5.19.20
    • CODESYS Control Runtime System Toolkit 3.5.19.20
    • CODESYS Control Win (SL) 3.5.19.20
    • CODESYS Development System 3.5.19.20
    • Codesys Hmi 3.5.19.20
    • CODESYS Safety SIL2 3.5.19.20

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    6.5

    CVSS v3

    Severity Medium on the scale from 0 to 10.

    Source: Schneider Electric, CVE.org

    0.6 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 50.0

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    55.68 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.6 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    50.0
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 11 October 2024
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-20

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    In multiple versions of multiple Codesys products, after successful authentication as a user, specific crafted network communication requests with inconsistent content can cause the CmpAppBP component to read internally from an invalid address, potentially leading to a denial-of-service condition. This vulnerability is different to CVE-2023-37553, CVE-2023-37554, CVE-2023-37555 and CVE-2023-37556.

    Source: schneider_csaf, NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    CODESYSCODESYS Control for BeagleBone SL
    • —
    • —
    CODESYSCODESYS Control for emPC-A/iMX6 SL
    • —
    • —
    CODESYSCODESYS Control for IOT2000 SL
    • —
    • —
    CODESYSCODESYS Control for Linux SL
    • —
    • —
    CODESYSCODESYS Control for PFC100 SL
    • —
    • —
    CODESYSCODESYS Control for PFC200 SL
    • —
    • —
    CODESYSCODESYS Control for PLCnext SL
    • —
    • —
    CODESYSCODESYS Control for Raspberry Pi SL
    • —
    • —
    CODESYSCODESYS Control for WAGO Touch Panels 600 SL
    • —
    • —
    CODESYSCODESYS Control RTE (for Beckhoff CX) SL
    • —
    • —
    CODESYSCODESYS Control RTE (SL)
    • —
    • —
    CODESYSCODESYS Control Runtime System Toolkit
    • —
    • —
    CODESYSCODESYS Control Win (SL)
    • —
    • —
    CODESYSCODESYS Development System V3
    • —
    • —
    CODESYSCODESYS HMI (SL)
    • —
    • —
    CODESYSCODESYS Safety SIL2 Runtime Toolkit
    • —
    • —
    codesyscontrol_for_beaglebone_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_empc-a\/imx6_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_iot2000_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_linux_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_pfc100_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_pfc200_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_plcnext_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_raspberry_pi_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_for_wago_touch_panels_600_sl
    • < 4.10.0.0
    • 4.10.0.0
    codesyscontrol_rte_sl
    • < 3.5.19.20
    • 3.5.19.20
    codesyscontrol_rte_sl_\(for_beckhoff_cx\)
    • < 3.5.19.20
    • 3.5.19.20
    codesyscontrol_runtime_system_toolkit
    • < 3.5.19.20
    • 3.5.19.20
    codesyscontrol_win_sl
    • < 3.5.19.20
    • 3.5.19.20
    codesysdevelopment_system
    • < 3.5.19.20
    • 3.5.19.20
    codesyshmi
    • < 3.5.19.20
    • 3.5.19.20
    codesyssafety_sil2
    • < 3.5.19.20
    • 3.5.19.20
    Schneider ElectricHarmony (Formerly Magelis) HMIGK/HMIGTO/HMIGTU/HMIGTUX/HMISTU series iPC series with Vijeo Designer runtime
    • 6.3 HF3
    • —
    Schneider ElectricHMISCU Controller
    • 6.3.1
    • —
    Schneider ElectricModicon Controller M241
    • 5.2.11.18
    • —
    Schneider ElectricModicon Controller M251
    • 5.2.11.18
    • —
    Schneider ElectricModicon Controller M262
    • 5.2.8.12
    • —
    Schneider ElectricPacDrive 3 Controllers: LMC Eco/Pro/Pro2
    • 1.76.14.1
    • —
    Schneider ElectricSoftSPS embedded in EcoStruxure™ Machine Expert
    • 2.2
    • —
    Schneider ElectricVijeo Designer Basic
    • 2.0 HotFix 2
    • —
    Schneider ElectricVijeo Designer embedded in EcoStruxure™ Machine Expert
    • 6.3.1
    • —
    Schneider ElectricVijeo Designer runtime
    • 6.3 SP2
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-20Improper Input Validation

      Class

      The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

      Entry at MITRE CWE-20

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2023-37552
    <a href="https://intel.neosec.eu/en/cve/CVE-2023-37552"><img src="https://intel.neosec.eu/badge/cve/CVE-2023-37552.svg?lang=en" alt="CVE-2023-37552 – NEOSEC Intel" height="20"></a>