CVE-2023-50274
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 · uneditedHPE OneView may allow command injection with local privilege escalation.
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 confidenceHPE OneView contains a command injection vulnerability that allows an attacker to execute arbitrary commands on the underlying system. Combined with local privilege escalation, this enables a local attacker to gain elevated (administrator/root) privileges by injecting malicious commands through the vulnerable interface.
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< 8.70CVSS 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 HPE OneView installationCheck for HPE OneView installation by looking for the OneView application directory, service, or process. Common locations include /opt/hpe/oneview or C:\Program Files\HPE\oneview on Windows. Also check for the 'oneview' service running via 'systemctl list-units --type=service | grep oneview' or 'Get-Service *oneview*' in PowerShell.Affected if HPE OneView software is found installed on the system
-
Determine installed OneView versionCheck the installed version using the OneView web interface (typically https://<appliance-ip>/#/about) or by running 'hponcfg -v' or checking the version file in the installation directory if accessible. Compare the version number against 8.70.Affected if Installed version is lower than 8.70 (for example, 8.60, 8.50, 7.x, etc.)
-
Verify vulnerable interface accessibilityThe command injection vulnerability exists in the OneView management interface. Check if the OneView web console (port 443/TCP or port 8000) is accessible. Review network access controls to determine if untrusted users could reach the management interface.Affected if The OneView management interface is accessible to untrusted local users or over the network
-
Check for signs of exploitationReview OneView appliance audit logs and system logs for unusual command execution, unexpected scripts, or spawning of shell processes. Look for commands containing suspicious patterns like semicolons, pipes, or command substitution in the logs.Affected if Suspicious commands or unexpected process spawns appear in logs associated with OneView components
The system is affected if HPE OneView version is installed and the version is below 8.70, making the command injection vulnerability potentially exploitable.
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 data8.70
Apply the HPE security patch for CVE-2023-50274 to the HPE OneView installation. Restrict local access to trusted personnel and monitor for unauthorized access attempts.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50274 — 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-50274 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