CVE-2022-26857
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 · uneditedDell OpenManage Enterprise Versions 3.8.3 and prior contain an improper authorization vulnerability. A remote authenticated malicious user with low privileges may potentially exploit this vulnerability to bypass blocked functionalities and perform unauthorized actions.
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 confidenceDell OpenManage Enterprise versions 3.8.3 and prior contain an improper authorization vulnerability where a remote authenticated user with low privileges can bypass blocked functionalities to perform unauthorized actions. This is a broken access control vulnerability allowing privilege escalation through insufficient authorization checks on certain API endpoints or functions.
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< 3.8.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 installed Dell OpenManage Enterprise versionAccess the OpenManage Enterprise web interface and navigate to the About or System information page, or use the REST API endpoint /api/ome/version to retrieve the installed version informationAffected if The installed version is 3.8.3 or any version prior to 3.8.4
-
Verify presence of low-privilege user accountsNavigate to User Management or Administration > Users in the OpenManage Enterprise console, or query the API endpoint /api/AccountService/Accounts to enumerate user accounts and their assigned rolesAffected if Any user account with non-administrative privileges (such as Read-Only, Operator, or custom low-privilege roles) exists in the system
-
Confirm API access controls are enforcedUsing a low-privilege authenticated user account, attempt to access administrative API endpoints such as /api/JobService/Jobs, /api/DeviceService/Devices, or /api/UpdateService/UpdateTargets that should be restricted to admin rolesAffected if Low-privilege users can successfully execute API calls that modify system configuration, create jobs, or access restricted resources without receiving authorization errors
-
Review user role assignments for privilege escalationCheck the role mappings for all users via the console or API endpoint /api/AccountService/Accounts and verify whether any low-privilege users have been granted administrative capabilitiesAffected if Users assigned to roles below Administrator level can perform actions that require Administrator permissions
A system is affected if it runs Dell OpenManage Enterprise version 3.8.3 or earlier AND has at least one low-privilege user account that can potentially escalate privileges through vulnerable API endpoints.
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 · scoped3.8.4
Upgrade to Dell OpenManage Enterprise version 3.9 or later, which contains the fix for this improper authorization vulnerability. If immediate upgrade is not possible, review and restrict low-privilege user permissions and monitor for suspicious administrative actions.
3.8.4
- Verify current OpenManage Enterprise version is 3.8.3 or prior by accessing the Dell OpenManage Enterprise console
- Plan maintenance window for upgrade (ensure backups are available)
- Download OpenManage Enterprise version 3.8.4 or later from Dell support portal (support.dell.com)
- Follow Dell's documented upgrade procedure for OpenManage Enterprise, typically via the console's firmware update or migration tool
- After upgrade, verify the new version is 3.8.4 or later and confirm the vulnerability is addressed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26857 — 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-26857 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