CVE-2023-6400
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 · uneditedIncorrect Authorization vulnerability in OpenText™ ZENworks Configuration Management (ZCM) allows Unauthorized Use of Device Resources.This issue affects ZENworks Configuration Management (ZCM) versions: 2020 update 3, 23.3, and 23.4.
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 confidenceThis is an Incorrect Authorization (broken access control) vulnerability in OpenText ZENworks Configuration Management that allows unauthorized users to access and use device resources they should not have permission to use. The vulnerability stems from insufficient authorization checks in the ZCM system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Physical
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:C/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.
-
Verify ZENworks Configuration Management is installedCheck for ZCM installation by looking for ZENworks services or the ZENworks installation directory. On Windows, check Services for 'ZENworks' services; on Linux, check for /opt/novell/zenworks or similar paths.Affected if ZENworks Configuration Management is present on the system
-
Identify the installed ZCM versionLocate the ZCM version information. This is typically found in the ZENworks Control Center, in installation logs, or via command-line tools such as 'zman' (ZENworks Administrator) if available. Compare your installed version to the affected version range.Affected if The installed version falls within the affected version range and has not been patched
-
In ZENworks Control Center, navigate to device resource access settings and verify that role-based access control (RBAC) or device access policies are enabled aAffected if Authorization controls are disabled or misconfigured, allowing unchecked access to device resources
-
Review audit logs for unauthorized access patternsAccess ZENworks audit logs (typically found in the ZENworks logging directory) and search for access events to device resources that may indicate the authorization bypass. Look for access from users or sessions that should not have permissions.Affected if Logs show device resource access by users lacking proper authorization entitlements
-
Verify device resource policies are properly scopedIn ZENworks Control Center, examine device resource policies and ensure they explicitly define allowed users and groups. Check that no policies exist with overly broad or unchecked access permissions.Affected if Device resource policies allow access to unauthorized users or groups
You are affected if ZENworks Configuration Management is installed with an unpatched version that falls within the affected range and has authorization controls that can be bypassed to access device resources without proper 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.
From vendor dataApply the vendor-supplied patches or updates for ZENworks Configuration Management to address the authorization bypass. Verify that device resource access controls are properly enforced after patching.
- Consultation8.0 h
- Implementation12.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6400 — 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-6400 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