CVE-2024-37131
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 · uneditedSCG Policy Manager, all versions, contains an overly permissive Cross-Origin Resource Policy (CORP) vulnerability. A remote unauthenticated attacker could potentially exploit this vulnerability, leading to the execution of malicious actions on the application in the context of the authenticated user.
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 confidenceSCG Policy Manager contains an overly permissive Cross-Origin Resource Policy (CORP) header that allows any origin to access resources. This CORP misconfiguration enables remote unauthenticated attackers to make cross-origin requests that could be executed in the context of an authenticated user, potentially leading to unauthorized actions or data exposure.
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.18.00.20, < 5.24.00.14CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed version of Dell Policy Manager For Secure Connect GatewayAccess the admin interface or check via CLI/API for the product version. This is typically found in the system information, about page, or via a version endpoint.Affected if The displayed version is 5.18.00.20 or higher but lower than 5.24.00.14
-
Compare version against the affected rangeVerify that the installed version falls within >= 5.18.00.20 and < 5.24.00.14Affected if The installed version is within this range, indicating the product is vulnerable
-
Inspect CORP header configurationMake an HTTP request to the Policy Manager web interface and examine the HTTP response headers for the Cross-Origin-Resource-Policy header. Use a browser dev tool or curl -I to view headers.Affected if The CORP header is set to 'unsafe' or 'null', or is missing entirely, allowing any origin to access resources
You are affected if the installed Dell Policy Manager For Secure Connect Gateway version is 5.18.00.20 or higher but lower than 5.24.00.14, and the CORP header permits cross-origin access from untrusted origins.
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.24.00.14
Configure a strict Cross-Origin Resource Policy (CORP) header restricting access to trusted origins only (e.g., 'same-origin' or explicit allowed origins), or remove the overly permissive setting entirely.
Policy Manager For Secure Connect Gateway version 5.24.00.14 or later
- 1. Backup the current Policy Manager configuration and database
- 2. Schedule a maintenance window for the upgrade
- 3. Download Dell Policy Manager for Secure Connect Gateway version 5.24.00.14 or later from the official Dell support site
- 4. Stop the Policy Manager service
- 5. Install the upgrade following Dell's standard upgrade procedures
- 6. Verify the CORP headers are properly configured after upgrade
- 7. Restart the Policy Manager service
- 8. Confirm the application is functioning correctly and the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37131 — 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-37131 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