dbcve.org
Hmibmuhi29d2801 FirmwareOperating system · Schneider Electric

CVE-2021-22817

HIGH · 7.8 CVSS v3.1 Published 2022-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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-276: Incorrect Default Permissions vulnerability exists that could cause unauthorized access to the base installation directory leading to local privilege escalation. Affected Product: Harmony/Magelis iPC Series (All Versions), Vijeo Designer (All Versions prior to V6.2 SP11 Multiple HotFix 4), Vijeo Designer Basic (All Versions prior to V1.2.1)

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 · high confidence

This is a CWE-276 Incorrect Default Permissions vulnerability where the base installation directory for Harmony/Magelis iPC, Vijeo Designer, and Vijeo Designer Basic has overly permissive file system access controls. This allows local, unauthorized users to read, modify, or replace executables, DLLs, or configuration files in the installation directory, enabling local privilege escalation to administrator or system privileges.

MitigationApply vendor patches (Vijeo Designer V6.2 SP11 HotFix 4 or later, Vijeo Designer Basic V1.2.1 or later) which修正 the default directory permissions to restrict access appropriately. For unsupported versions, manually harden directory permissions to remove unnecessary access rights.

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
Hmibmuhi29d2801 FirmwareOperating system
Affected:all versions
Hmibmusi29d2801 FirmwareOperating system
Affected:all versions
Hmibmuci29d2w01 FirmwareOperating system
Affected:all versions
Hmibmu0i29d2001 FirmwareOperating system
Affected:all versions
Hmibmu0i29d200a FirmwareOperating system
Affected:all versions
Hmibmuhi29d4801 FirmwareOperating system
Affected:all versions
Hmibmusi29d4801 FirmwareOperating system
Affected:all versions
Hmibmuci29d4w01 FirmwareOperating system
Affected:all versions

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Schneider Electric HMI software is installed
    Check common installation paths for Vijeo Designer, Vijeo Designer Basic, or Harmony/Magelis iPC software. Typical paths include C:\Program Files\Schneider Electric\Vijeo Designer or C:\Program Files (x86)\Schneider Electric\Vijeo Designer. Also check C:\Program Files\Schneider Electric\ and subdirectories for Hmibm* firmware folders.
    Affected if The Schneider Electric HMI software or firmware folders (Hmibmuhi29d2801, Hmibmusi29d2801, Hmibmuci29d2w01, Hmibmu0i29d2001, Hmibmu0i29d200a, Hmibmuhi29d4801, Hmibmusi29d4801, Hmibmuci29d4w01) are present on the system.
  2. Locate the installation directory
    Use Windows Explorer or command 'dir /s /b "C:\Program Files\Schneider Electric" 2>nul' and 'dir /s /b "C:\Program Files (x86)\Schneider Electric" 2>nul' to find all Schneider Electric installation directories.
    Affected if A Schneider Electric software installation directory exists on the system.
  3. Check directory permissions for overly permissive access
    Right-click the installation directory, go to Properties > Security tab. Examine the permissions for groups such as Everyone, Users, and Authenticated Users. Use 'icacls <directory>' from an elevated command prompt to view detailed ACLs.
    Affected if The installation directory grants Write or Modify permissions to Everyone, Users, or other non-administrator groups.
  4. Verify executable and DLL file permissions
    Use 'icacls "<install_dir>\*.exe"' and 'icacls "<install_dir>\*.dll"' to check if non-admin users have write access to executables or DLLs in the installation folder.
    Affected if Non-administrator users can modify, replace, or write to executable (.exe) or dynamic-link library (.dll) files in the installation directory.
  5. Confirm vulnerability from standard user perspective
    Log in as a non-administrator user (or use 'runas /user:StandardUser cmd.exe') and attempt to create or modify a file in the installation directory, or use 'accesschk.exe -dqw <directory>' if available.
    Affected if A standard (non-privileged) user can write, modify, or delete files in the installation directory.

If the Schneider Electric HMI software is installed and the installation directory grants Write or Modify permissions to non-administrator users, the environment is affected by this incorrect default permissions vulnerability.

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 vendor patches (Vijeo Designer V6.2 SP11 HotFix 4 or later, Vijeo Designer Basic V1.2.1 or later) which修正 the default directory permissions to restrict access appropriately. For unsupported versions, manually harden directory permissions to remove unnecessary access rights.

Fix this in Hmibmuhi29d2801 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22817 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2021-22817 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