Openmanage Network IntegrationApplication · Dell

CVE-2025-36593

HIGH · 8.8 CVSS v3.1 Published 2025-06-30
Fix available
A fix is available. Upgrade to 3.8 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Dell OpenManage Network Integration, versions prior to 3.8, contains an Authentication Bypass by Capture-replay vulnerability in the RADIUS protocol. An attacker with local network access could potentially exploit this vulnerability to forge a valid protocol accept message in response to a failed authentication request.

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 confidence

This is a capture-replay vulnerability in the RADIUS protocol implementation of Dell OpenManage Network Integration. An attacker with local network access can capture a valid RADIUS Access-Accept message from a previous successful authentication and replay it to bypass authentication, allowing unauthorized access without knowing valid credentials.

MitigationUpgrade Dell OpenManage Network Integration to version 3.8 or later. As a temporary measure, ensure strict network access controls to limit who can intercept RADIUS traffic on the local network.

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
Openmanage Network IntegrationApplication
Affected:< 3.8

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Dell OpenManage Network Integration is installed
    Locate the product installation directory or check installed programs list for Dell OpenManage Network Integration
    Affected if The product is installed on the system
  2. Check installed version against affected range
    Identify the installed version of Dell OpenManage Network Integration and compare it to the affected range (versions prior to 3.8)
    Affected if Installed version is lower than 3.8
  3. Verify RADIUS authentication is configured
    Inspect the product configuration for RADIUS authentication settings - look for RADIUS server definitions and authentication policy configuration
    Affected if RADIUS authentication is enabled and configured as an authentication method
  4. Confirm RADIUS message authenticator is not in use
    Examine RADIUS configuration for the Message-Authenticator attribute (attribute type 80) - check whether Message-Authenticator validation is enabled or disabled
    Affected if RADIUS is in use without Message-Authenticator attribute validation (the vulnerability requires RADIUS without this protection)

The environment is affected if Dell OpenManage Network Integration version低于3.8 is installed with RADIUS authentication enabled but without Message-Authenticator attribute validation protecting against replay attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.8 or later
Fixed in 3.8
Interim mitigation

Upgrade Dell OpenManage Network Integration to version 3.8 or later. As a temporary measure, ensure strict network access controls to limit who can intercept RADIUS traffic on the local network.

Recommended fix High confidence

3.8

  1. 1. Backup the current Dell OpenManage Network Integration configuration and settings
  2. 2. Download Dell OpenManage Network Integration version 3.8 from Dell Support (support.dell.com)
  3. 3. Stop the Dell OpenManage Network Integration service
  4. 4. Install the version 3.8 upgrade package
  5. 5. Verify the installation completed successfully
  6. 6. Restart the Dell OpenManage Network Integration service
  7. 7. Confirm the RADIUS authentication is functioning correctly with the new version
Caveat Review Dell release notes for version 3.8 for any configuration changes or migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openmanage Network Integration Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-36593 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-36593 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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