CVE-2024-28966
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 SCG, versions prior to 5.24.00.00, contain an Improper Access Control vulnerability in the SCG exposed for an internal update REST API (if enabled by Admin user from UI). A remote low privileged attacker could potentially exploit this vulnerability, leading to the execution of certain APIs applicable only for Admin Users on the application's backend database that could potentially allow an unauthorized user access to restricted resources and change of state.
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 SCG contains an improper access control vulnerability in its internal update REST API (when enabled by an admin from the UI). A remote low-privileged attacker can bypass authorization checks and execute admin-level APIs on the backend database, allowing unauthorized access to restricted resources and modification of system state.
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.22.00.18CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Dell SCG versionLocate the installed version in the admin UI under System > About or Settings > Diagnostics, or use the appropriate CLI command to retrieve the firmware versionAffected if Version number falls between 5.18.00.20 and 5.22.00.18 inclusive
-
Check internal update REST API statusAccess the admin UI and navigate to the settings area where the internal update REST API can be configured (typically under System Settings, Update Configuration, or similar). Determine whether the internal update REST API toggle is currently enabled.Affected if Internal update REST API is enabled by the administrator
You are affected only if the installed Dell SCG version is within 5.18.00.20 to 5.22.00.18 AND the internal update REST API has been enabled from the admin UI.
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 · scopedUpgrade Dell SCG to version 5.24.00.00 or later. If the internal update REST API is not required, disable it via the admin UI to reduce attack surface.
Dell Secure Connect Gateway version 5.24.00.00 or later
- 1. Log in to the Dell Secure Connect Gateway (SCG) admin console as an administrator.
- 2. Navigate to the system settings or administration section.
- 3. Check the current installed version under System > About or similar location.
- 4. Download the Dell Secure Connect Gateway version 5.24.00.00 or later from the Dell support portal (support.dell.com).
- 5. Follow Dell's standard upgrade procedure for SCG - this typically involves uploading the upgrade bundle through the admin UI or using the CLI upgrade command.
- 6. Verify the upgrade completed successfully by checking the system version again.
- 7. Confirm the internal update REST API feature is still functioning as expected if it was previously enabled.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28966 — 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-28966 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