CVE-2023-6407
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 · uneditedA CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause arbitrary file deletion upon service restart when accessed by a local and low-privileged attacker.
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 confidenceA path traversal (CWE-22) vulnerability allows a local low-privileged attacker to delete arbitrary files on the system through improper path validation. The arbitrary file deletion is triggered upon service restart, indicating the vulnerability likely involves how the service handles file paths during its startup or recovery sequence.
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< 2.6-ga-01-23248CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Identify if Schneider Electric Easy Ups Online Monitoring Software is installedCheck installed programs or application list for 'Schneider Electric Easy Ups Online Monitoring Software' or look for the application executable in Program Files directoriesAffected if The software is present on the system
-
Determine the installed versionLocate the application's version information through its About/Properties window, installer logs, or registry entries under the software's installation pathAffected if The version is lower than 2.6-ga-01-23248 (e.g., 2.5-x, 2.4-x, etc.)
-
Verify the service account permissionsCheck the file system permissions on sensitive directories (system32, user profile folders) granted to the user account running the Easy Ups Online serviceAffected if The service runs under an account with elevated file deletion permissions beyond its operational scope
-
Inspect service configuration for path handlingExamine service configuration files, logs, or startup scripts in the installation directory for file path references that might accept user-controlled inputAffected if Configuration files contain unsanitized path parameters that could be manipulated with traversal sequences (../)
-
Check service restart accessibilityDetermine if low-privileged users can trigger service restart or if the service auto-restarts on failure, as exploitation occurs during service restartAffected if The service can be restarted by low-privileged users or automatically restarts without administrative oversight
The environment is affected if Schneider Electric Easy Ups Online Monitoring Software version lower than 2.6-ga-01-23248 is installed and the service account has broad file deletion permissions.
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 · scoped2.6-ga-01-23248
Implement strict input validation and canonicalization of all file paths to prevent traversal sequences (../). Additionally, enforce principle of least privilege on file system permissions to limit what the service account can delete.
2.6-ga-01-23248 or later
- 1. Navigate to the official Schneider Electric download portal at download.schneider-electric.com
- 2. Locate and download Easy Ups Online Monitoring Software version 2.6-ga-01-23248 or later
- 3. Back up the current Easy Ups Online Monitoring Software configuration and data
- 4. Stop the Easy Ups Online Monitoring Software service
- 5. Install the downloaded version 2.6-ga-01-23248
- 6. Start the Easy Ups Online Monitoring Software service
- 7. Verify the service is running correctly and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-6407 — 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-2023-6407 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