CVE-2025-24381
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 Unity, version(s) 5.4 and prior, contain(s) an URL Redirection to Untrusted Site ('Open Redirect') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to a targeted application user being redirected to arbitrary web URLs. The vulnerability could be leveraged by attackers to conduct phishing attacks that cause users to divulge sensitive information. Exploitation may allow for session theft.
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 Unity versions 5.4 and prior contain an open redirect vulnerability where an unauthenticated remote attacker can craft malicious URLs that redirect users to arbitrary external websites. This occurs due to insufficient validation of redirect parameters in the web interface, allowing attackers to leverage the trusted Dell Unity domain in phishing campaigns to steal user credentials or session tokens.
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< 5.5.0.0.5.259CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Determine the installed Dell Unity versionLog into the Dell Unity system via SSH or console and run the command 'system version' or check the web interface login page footer for the version display. Alternatively, access the Unisphere management UI and navigate to Settings > About to view the firmware version.Affected if The displayed version is 5.4.x or any version number lower than 5.5.0.0.5.259, indicating the installation falls within the vulnerable range.
-
Confirm web interface accessibilityVerify that the Unisphere web interface is enabled and reachable. Check via the CLI command 'service -status' or by attempting to access the Unisphere URL (typically https://<unity-ip>) from an authorized network.Affected if The Unisphere web interface is accessible over the network, as the open redirect vulnerability exploits the web interface redirect parameters.
-
Identify exposed management interfacesReview network configuration by running 'networkinterface -list' or checking the firewall rules to determine which management ports (HTTP/HTTPS) are open and accessible from external networks.Affected if Ports 80, 443, or the Unisphere management service are exposed to untrusted networks, increasing the attack surface for unauthenticated redirect exploitation.
If the installed Dell Unity version is 5.4 or any version below 5.5.0.0.5.259 and the web management interface is accessible, the environment is affected by this open redirect vulnerability.
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 · scoped5.5.0.0.5.259
Apply the vendor-supplied patch or upgrade Dell Unity to a version beyond 5.4. Additionally, implement URL validation at the web application or proxy layer to block redirects to untrusted external domains until the patch can be applied.
5.5.0.0.5.259 or later
- 1. Back up all critical data and configurations on the current Dell Unity system
- 2. Review Dell Unity 5.5.0.0.5.259 release notes for any prerequisites or known issues
- 3. Schedule a maintenance window for the upgrade procedure
- 4. Download the Unity Operating Environment version 5.5.0.0.5.259 or later from Dell support portal (support.dell.com)
- 5. Follow Dell's documented upgrade procedure for Unity OE, typically via the Unisphere web interface or CLI
- 6. Verify the upgrade completed successfully by checking the system version
- 7. Test that the open redirect vulnerability is no longer present by attempting to verify the fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24381 — 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-2025-24381 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