CVE-2022-0556
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 local privilege escalation vulnerability caused by incorrect permission assignment in some directories of the Zyxel AP Configurator (ZAC) version 1.1.4, which could allow an attacker to execute arbitrary code as a local administrator.
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 confidenceZyxel AP Configurator (ZAC) version 1.1.4 contains incorrect permission assignments on certain directories that allow local unprivileged users to modify executable files or inject code that runs with local administrator privileges, enabling privilege escalation.
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= 1.1.4CVSS 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.
-
Identify if Zyxel AP Configurator is installedSearch for ZAC installation directory in common locations such as C:\Program Files\Zyxel or C:\Program Files (x86)\Zyxel, or use system registry queries or installed programs listAffected if ZAC is found installed on the system
-
Confirm installed version is 1.1.4Locate version information in the ZAC installation directory, typically in an About dialog, version.txt file, or executable properties (right-click on ZAC executable and select Properties > Details)Affected if The installed version is exactly 1.1.4
-
List directory permissions on ZAC installation folderRight-click the ZAC installation folder, select Properties > Security tab, and review the permissions for Users and other non-administrator groups. Alternatively, run 'icacls "<ZAC_install_path>"' from command promptAffected if Non-admin users have Write or Modify permissions on directories containing executable files
-
Identify writable directories accessible to non-admin usersRun 'icacls "<ZAC_install_path>\*" /t' to recursively list all permissions, looking for entries showing (CI)(OI)(W) or similar write permissions granted to Users or Authenticated UsersAffected if Any directory under the ZAC installation path grants Write access to non-privileged users
-
Check executable file permissions for modification accessReview permissions on .exe and .dll files within the ZAC directory - right-click each executable, check Security tab, or run 'icacls "<path_to_exe>"' to see if Users group has Modify or Write permissionsAffected if Executables in the ZAC directory are modifiable by non-admin users (Users group has Modify or Write permissions listed)
The environment is affected if Zyxel AP Configurator version 1.1.4 is installed AND the ZAC installation directory grants non-administrator users Write or Modify permissions to directories containing executable files.
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 dataApply vendor patches when available; otherwise, audit and remediate directory ACLs in the ZAC installation directory to enforce least-privilege permissions, removing write access for non-admin users.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0556 — 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-2022-0556 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