Schneider Electric
EcoStruxure Foxboro DCS Core Control Services
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2024-5681 | 11 Jul 2024 | Versions 9.8 and prior | Patch HF97872598 available for v9.5 to v9.8 of EcoStruxureTM Foxboro DCS Core Control Services includes a fix for these vulnerabilities. Please contact your local Service Representative or Schneider Electric Process Automation Global Customer Support Center for information on how to download and install this fix: | Update reference ↗ |
| CVE-2024-5680 | 11 Jul 2024 | Versions 9.8 and prior | Patch HF97872598 available for v9.5 to v9.8 of EcoStruxureTM Foxboro DCS Core Control Services includes a fix for these vulnerabilities. Please contact your local Service Representative or Schneider Electric Process Automation Global Customer Support Center for information on how to download and install this fix: | Update reference ↗ |
| CVE-2024-5679 | 11 Jul 2024 | Versions 9.8 and prior | Patch HF97872598 available for v9.5 to v9.8 of EcoStruxureTM Foxboro DCS Core Control Services includes a fix for these vulnerabilities. Please contact your local Service Representative or Schneider Electric Process Automation Global Customer Support Center for information on how to download and install this fix: | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.