CVE-2024-37130
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 Server Administrator, versions 11.0.1.0 and prior, contains a Local Privilege Escalation vulnerability via XSL Hijacking. A local low-privileged malicious user could potentially exploit this vulnerability and escalate their privilege to the admin user and gain full control of the machine. Exploitation may lead to a complete system compromise.
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 confidenceDell OpenManage Server Administrator versions 11.0.1.0 and prior suffer from a Local Privilege Escalation vulnerability via XSL Hijacking. The vulnerability allows a low-privileged local user to manipulate XSLT stylesheet processing to execute arbitrary code with elevated (administrator) privileges, achieving full system compromise.
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<= 11.0.1.0CVSS 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.
-
Confirm Dell OpenManage Server Administrator is installedCheck for OMSA installation by looking in typical installation directories (Windows: C:\Program Files\Dell\SysMgt, Linux: /opt/dell/ or /usr/local/dell/) or search for 'OpenManage' in installed programsAffected if Dell OpenManage Server Administrator is present on the system
-
Identify the installed version of Dell OpenManage Server AdministratorRun the command to retrieve OMSA version information, such as 'omconfig about' or 'omreport system version' on Linux, or check Add/Remove Programs on Windows for the version numberAffected if The installed version cannot be determined or shows as 11.0.1.0 or any version prior to it
-
Compare installed version against affected rangeIf version is obtained, verify whether it is 11.0.1.0 or lower (any version number less than or equal to 11.0.1.0 is affected)Affected if The installed version is 11.0.1.0 or any prior version (e.g., 11.0.0.0, 10.x.x.x, 9.x.x.x)
-
Check if the web interface or XML/XSLT service is enabledVerify whether the OMSA web server service (usually 'DSM OmSrv' or similar) is running and the XML/XSL transformation functionality is accessible via the web interfaceAffected if The OMSA web service is running and accessible to the local user
-
Review local user privileges and access controlsCheck which local users have access to the OMSA installation directory and web interface, particularly looking for low-privileged accounts that could potentially exploit the XSL Hijacking flawAffected if Low-privileged local users have access to the OMSA installation or web interface
You are affected if Dell OpenManage Server Administrator is installed and the installed version is 11.0.1.0 or any earlier version, especially if the web interface or XML/XSLT service is accessible to local users.
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 patch for CVE-2024-37130 when available, or upgrade to a patched version of Dell OpenManage Server Administrator. Restrict local access to trusted users and monitor for unauthorized privilege escalation attempts until a fix is deployed.
- 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-2024-37130 — 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-2024-37130 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