CVE-2022-23858
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 flaw was found in the REST API. An improperly handled REST API call could allow any logged user to elevate privileges up to the system account. This affects StarWind Command Center build 6003 v2.
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 confidenceThe REST API in StarWind Command Center build 6003 v2 contains an improper authorization vulnerability that allows any authenticated user to escalate their privileges to system account level through specially crafted API calls.
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= 2CVSS 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 StarWind Command Center installationCheck for StarWind Command Center in installed programs (Windows: Control Panel > Programs and Features, or check C:\Program Files\StarWind\ or C:\Program Files (x86)\StarWind\)Affected if StarWind Command Center version 2 build 6003 is installed and running
-
Verify the exact build versionOpen the application or check version information in the installation directory for the build number. Typically found in an About section or in the executable properties.Affected if The installed build is exactly 6003 (the vulnerable version)
-
Confirm REST API is accessibleCheck if the REST API endpoint is exposed (default port 8081 or 8000, depending on configuration). Attempt a simple authenticated request to the API endpoint.Affected if The REST API is enabled and accessible on the network or localhost
-
Review user accounts for unexpected system-level privilegesCheck the StarWind Command Center user management interface or user configuration files for accounts with system administrator privileges that were not intentionally assigned or that exceed normal user permissions.Affected if There are user accounts with system-level privileges that were not deliberately created or assigned by an administrator
-
Examine API access logs for privilege escalation patternsReview StarWind Command Center logs (typically in the logs/ directory) for API calls that include authorization header manipulation, role modification requests, or privilege escalation attempts from standard user accounts.Affected if Logs show API calls from standard users attempting or successfully modifying their privileges or accessing system-level functions
You are affected if StarWind Command Center version 2 build 6003 is installed and the REST API is accessible, particularly if unauthorized system-level accounts exist or API logs show privilege escalation activity.
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 dataThe vendor should implement proper role-based authorization checks in the REST API to enforce privilege boundaries and prevent authenticated users from escalating beyond their assigned permissions.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23858 — 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-23858 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