CVE-2024-0157
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 Storage Resource Manager, 4.9.0.0 and below, contain(s) a Session Fixation Vulnerability in SRM Windows Host Agent. An adjacent network unauthenticated attacker could potentially exploit this vulnerability, leading to the hijack of a targeted user's application session.
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 confidenceThis is a Session Fixation vulnerability in Dell Storage Resource Manager's Windows Host Agent. An adjacent network attacker can potentially set or fix a user's session ID before authentication occurs, allowing the attacker to hijack the user's session after they log in. The vulnerability is exploitable by an unauthenticated attacker on the adjacent 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< 5.0.0.0< 5.0.0.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 if Dell Storage product is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' to list installed software. Look for 'Dell Storage Monitoring And Reporting' or 'Dell Storage Resource Manager'.Affected if Either product is listed in installed programs
-
Check installed version against vulnerable rangeIn Programs and Features, check the version column for the Dell Storage product. Alternatively, right-click the application's executable (typically in Program Files\Dell) and view Properties > Details to find the File Version.Affected if The installed version is any version lower than 5.0.0.0, or if the version cannot be determined and the product is installed
-
Verify the Windows Host Agent service is runningOpen Services (services.msc) and look for 'Dell Storage Resource Manager Host Agent' or 'Dell Storage Monitoring And Reporting Host Agent' service. Check if the Status is 'Running'.Affected if The Host Agent service is installed and running on the system
-
Determine network exposure of web interfaceFrom another system on the same network segment, attempt to access the product's web interface using the IP address or hostname of the affected server (typically ports 8443, 443, or 8080). Use a browser or curl command: 'curl -k https://<server>:8443'Affected if The web interface is reachable from an adjacent network segment without authentication, indicating the attack surface is exposed
-
Inspect session cookie behavior before authenticationUsing a browser's developer tools (F12), clear cookies, then navigate to the login page of the Dell Storage web interface WITHOUT logging in. Check the Application/Storage tab for any session cookies (JSESSIONID, ASP.NET_SessionId, or similar) that were set prior to authentication.Affected if A session identifier cookie is created and assigned to the browser BEFORE the user authenticates, indicating the session fixation vulnerability is present
The environment is affected if Dell Storage Resource Manager or Dell Storage Monitoring And Reporting is installed with a version lower than 5.0.0.0 and the Host Agent service is running with network-accessible web interface.
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.0.0.0
Implement session ID regeneration upon user authentication and invalidate any pre-existing session identifiers to prevent fixation attacks. Additionally, consider implementing session timeout and secure session cookie attributes.
Dell Storage Resource Manager 5.0.0.0
- Back up current Storage Resource Manager configuration and data
- Review Dell Storage Resource Manager 5.0.0.0 release notes for any pre-upgrade requirements
- Ensure system meets hardware and software prerequisites for version 5.0.0.0
- Download Dell Storage Resource Manager 5.0.0.0 from Dell support portal
- Stop SRM services on the Windows host agent
- Install version 5.0.0.0 following Dell upgrade documentation
- Verify SRM services start successfully
- Validate that the session fixation vulnerability is resolved by confirming new session tokens are generated on login
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0157 — 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-0157 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