CVE-2024-2747
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-428: Unquoted search path or element vulnerability exists in Easergy Studio, which could cause privilege escalation when a valid user replaces a trusted file name on the system and reboots the machine.
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 confidenceEasergy Studio contains a CWE-428 unquoted service path vulnerability that allows a local authenticated user to achieve privilege escalation by placing a malicious executable in an unquoted path location and triggering execution upon system reboot.
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.3.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Easergy Studio installationCheck for Schneider Electric Easergy Studio in Windows installed programs (Add/Remove Programs) or look in C:\Program Files\Schneider Electric\Easergy Studio for the application directoryAffected if Easergy Studio is not present on the system, the vulnerability does not apply
-
Identify installed versionCheck the version of Easergy Studio by right-clicking the executable in the installation directory and selecting Properties, or check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the version entryAffected if Version is 9.3.3 or lower (any version up to and including 9.3.3)
-
Enumerate Easergy Studio Windows servicesOpen Command Prompt or PowerShell and run: sc query type= service state= all | findstr /i "Easergy" or Get-Service | Where-Object {$_.DisplayName -like "*Easergy*"}Affected if No services with 'Easergy' in the name are found, the vulnerability does not apply
-
Inspect service binary paths for unquoted pathsFor each Easergy service found, run: sc qc <ServiceName> (or check Registry at HKLM\SYSTEM\CurrentControlSet\Services\<ServiceName> for the ImagePath value). Examine the binary path for spaces that are NOT enclosed in quotesAffected if The service binary path contains spaces without surrounding quotes (e.g., C:\Program Files\Schneider Electric\Easergy Studio\service.exe instead of "C:\Program Files\Schneider Electric\Easergy Studio\service.exe")
-
Verify service is configured to startRun: sc qc <ServiceName> and check the START_TYPE field, or run Get-Service -Name <ServiceName> | Select-Object Status,StartTypeAffected if Service is set to auto-start (START_TYPE: AUTO_START) or manual start, meaning it could execute upon system reboot with the unquoted path vulnerability
You are affected if Easergy Studio version 9.3.3 or lower is installed AND one or more of its Windows services have unquoted binary paths containing spaces.
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.
From vendor dataRestrict write permissions on directories in the service path to prevent unauthorized file replacement, and verify all service paths use quoted strings in service configurations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2747 — 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-2747 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