dbcve.org
Ecostruxure Foxboro Dcs Control Core ServicesApplication · Schneider Electric

CVE-2023-2570

HIGH · 7.8 CVSS v3.1 Published 2023-06-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A CWE-129: Improper Validation of Array Index vulnerability exists that could cause local denial-of-service, and potentially kernel execution when a malicious actor with local user access crafts a script/program using an unpredictable index to an IOCTL call in the Foxboro.sys driver.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A CWE-129 Improper Validation of Array Index vulnerability exists in the Foxboro.sys driver where a local attacker can craft a malicious script/program using an unpredictable index to an IOCTL call. This could cause local denial-of-service and potentially allow kernel-level code execution.

MitigationApply vendor-provided patches for the Foxboro driver. If no patch is available, restrict local user access to the affected system, disable the driver if unnecessary, or implement input validation controls at the application layer to prevent malicious IOCTL requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ecostruxure Foxboro Dcs Control Core ServicesApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Foxboro.sys driver file
    Search for Foxboro.sys in system driver directories: %SystemRoot%\System32\drivers\ on Windows or /lib/modules/ on Linux. Use 'dir /s C:\Foxboro.sys' or 'find / -name Foxboro.sys' respectively.
    Affected if The Foxboro.sys file exists on the system, indicating the driver is installed.
  2. Check if the Foxboro driver service exists
    On Windows, run 'sc query Foxboro' or check the Windows Registry under HKLM\SYSTEM\CurrentControlSet\Services for a service entry related to Foxboro. On Linux, check for a Foxboro-related service using 'systemctl list-units --all | grep -i foxboro' or inspect /etc/init.d/ for startup scripts.
    Affected if A Foxboro driver service or driver entry exists in the system services or registry.
  3. Verify if the driver is currently loaded
    On Windows, run 'sc query type= driver' to list loaded drivers and search for Foxboro. On Linux, run 'lsmod | grep -i foxboro' to check if the kernel module is loaded, or check /proc/modules.
    Affected if The Foxboro driver is currently loaded in memory as an active kernel module.
  4. Identify any processes or applications using the driver
    Review running processes that may communicate with the Foxboro driver, particularly EcoStruxure Foxboro DCS Control Core Services. Check for process names like 'Foxboro' or 'ControlCoreServices' in Task Manager (Windows) or via 'ps aux | grep -i foxboro' (Linux).
    Affected if Processes associated with Ecostruxure Foxboro DCS are running on the system.
  5. Check for exposed IOCTL interfaces
    Use Sysinternals Process Explorer or equivalent tools to inspect open handles to the Foxboro.sys driver. On Windows, run 'winobj' or use 'handle' utility to search for handles named 'Foxboro'. On Linux, check /proc/[pid]/fd for file descriptors linking to the driver.
    Affected if IOCTL handles or device interfaces to Foxboro.sys are accessible from user-mode processes.

The system is affected if the Foxboro.sys driver is installed, loaded, or actively running as part of EcoStruxure Foxboro DCS Control Core Services, as the vulnerability requires the driver to be present for the IOCTL array index flaw to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches for the Foxboro driver. If no patch is available, restrict local user access to the affected system, disable the driver if unnecessary, or implement input validation controls at the application layer to prevent malicious IOCTL requests.

Fix this in Ecostruxure Foxboro Dcs Control Core Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2570 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-2570 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data