CVE-2024-5679
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 · uneditedCWE-787: Out-of-Bounds Write vulnerability exists that could cause local denial-of-service, or kernel memory leak when a malicious actor with local user access crafts a script/program using 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 confidenceAn out-of-bounds write vulnerability (CWE-787) exists in the Foxboro.sys kernel driver where a local attacker with user-level access can craft malicious IOCTL calls to trigger the vulnerability, potentially causing kernel memory leaks or local denial-of-service conditions.
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<= 9.8CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Foxboro.sys driver fileSearch for Foxboro.sys in system driver directories: C:\Windows\System32\drivers\ and review installed program directories for Foxboro DCS componentsAffected if The Foxboro.sys driver file exists on the system
-
Check installed Ecostruxure Foxboro DCS versionInspect the installed version of 'Schneider Electric Ecostruxure Foxboro DCS Control Core Services' via Windows Programs and Features, or query the installed packages using registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or the program's executable version infoAffected if The installed version is 9.8 or lower, or if version cannot be determined but the product is present
-
Verify Foxboro.sys driver loaded stateRun 'sc query foxboro' or check driver loaded status via 'driverquery /v | findstr -i foxboro' in an administrative command promptAffected if The Foxboro.sys driver is in a RUNNING or STARTED state
-
Confirm local user access scopeReview system local user/group membership and privileges granted to users who have access to the system hosting this serviceAffected if Multiple untrusted local users exist with user-level access to the system where Foxboro DCS is installed
-
Audit IOCTL interface exposureUse tools like Sysinternals Process Monitor or kernel debugger to observe IOCTL calls (0x9C402000 range typically) sent to the Foxboro.sys driver device object (\\.\FoxboroDevice or similar)Affected if IOCTL calls to the driver can be issued by non-privileged user processes without filtering
A system is affected if Foxboro.sys driver is present and the Ecostruxure Foxboro DCS Control Core Services version is 9.8 or lower, with local user access enabled to the driver interface.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedRestrict local user access to systems with this driver, implement IOCTL call filtering/validation, and apply vendor-provided patches when available. Consider disabling the driver if not required.
Version greater than 9.8 (latest available release from Schneider Electric)
- 1. Identify the current installed version of Ecostruxure Foxboro DCS Control Core Services by checking the system or consulting the system inventory
- 2. Download the latest available version of Ecostruxure Foxboro DCS Control Core Services from the Schneider Electric download portal at download.schneider-electric.com
- 3. Review the release notes and upgrade documentation for any specific prerequisites or migration considerations
- 4. Create a complete backup of the current system configuration and any critical data
- 5. Schedule a maintenance window appropriate for a control system update
- 6. Follow Schneider Electric's standard upgrade procedure for Foxboro DCS Control Core Services
- 7. After upgrade, verify the Foxboro.sys driver version corresponds to the patched release
- 8. Test that the system operates normally and the IOCTL functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5679 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5679 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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