Galaxy Vl FirmwareOperating system · Schneider Electric

CVE-2023-6032

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability exists that could cause a file system enumeration and file download when an attacker navigates to the Network Management Card via HTTPS.

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 path traversal vulnerability (CWE-22) in the APC Network Management Card web interface allows remote attackers to access files outside the intended restricted directory via specially crafted HTTP requests, enabling file system enumeration and arbitrary file download.

MitigationApply the vendor firmware update from Schneider Electric/APC that addresses input validation in the web application's file handling logic, and restrict web interface access to trusted networks via firewall rules as an interim control.

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
Galaxy Vl FirmwareOperating system
Affected:= 12.21
Galaxy Vs FirmwareOperating system
Affected:= 6.82

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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. Identify the installed firmware version
    Access the APC Network Management Card web interface and navigate to the About or System Information page to view the firmware version. Alternatively, use the device's command-line interface or SNMP to retrieve the firmware version string.
    Affected if The firmware version is 12.21 or later for Schneider Electric Galaxy Vl, or 6.82 or later for Schneider Electric Galaxy Vs.
  2. Confirm the web interface is enabled
    Verify that the embedded web server (EcoStruxure IT Gateway or APC embedded web server) is actively running by attempting to access the device's IP address on HTTP/HTTPS ports 80 or 443, or check the network configuration via the management interface.
    Affected if The web interface is enabled and accessible on any network interface.
  3. Determine network exposure of the management interface
    Review firewall rules, access control lists, or network segmentation policies that control access to the device's web interface ports. Check if the management IP is reachable from untrusted networks or the internet.
    Affected if The web interface is reachable from networks outside the trusted management network.
  4. Inspect web server access logs for path traversal patterns
    If accessible, review the APC device's web server logs or centralized logging systems for requests containing sequences such as ../, ..\, or absolute path patterns that may indicate exploitation attempts.
    Affected if Logs contain HTTP requests with directory traversal patterns targeting system files outside the web root.

You are affected if your Galaxy Vl runs firmware >= 12.21 or Galaxy Vs runs firmware >= 6.82 AND the web interface is enabled and accessible.

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 the vendor firmware update from Schneider Electric/APC that addresses input validation in the web application's file handling logic, and restrict web interface access to trusted networks via firewall rules as an interim control.

Fix this in Galaxy Vl Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6032 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6032 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