CVE-2024-28965
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 enable 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 Internal 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 Security Gateway (SCG) versions prior to 5.24.00.00 have an improper access control vulnerability where an internal REST API, when enabled by an administrator through the UI, can be accessed by remote low-privileged attackers. This allows unauthorized execution of admin-level Internal APIs on the backend database, enabling access to restricted resources and state changes.
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 the installed Dell SCG versionAccess the Dell Secure Connect Gateway management UI or use the system information command in the CLI to retrieve the current firmware/software versionAffected if The version is 5.18.00.20 through 5.22.00.18 (any version prior to 5.24.00.00 within the listed range)
-
Confirm the specific version rangeCompare your installed version number against the affected range: versions 5.18.00.20, 5.18.00.21, 5.18.00.22, up to 5.22.00.18Affected if Your installed version matches or falls between 5.18.00.20 and 5.22.00.18 inclusive
-
Locate the internal REST API configurationNavigate to the Dell SCG management UI and locate the settings section where administrative features or REST API options are configuredAffected if The internal REST API feature toggle is currently enabled (turned on)
-
Verify API accessibilityAttempt to access the internal REST API endpoint from a remote location using a low-privileged account or unauthenticated requestAffected if The API responds to remote requests without requiring admin-level authentication, indicating the vulnerability is exploitable
You are affected if your Dell Secure Connect Gateway runs version 5.18.00.20 through 5.22.00.18 AND the internal REST API feature is enabled in the 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 · scopedApply vendor patch by upgrading Dell SCG to version 5.24.00.00 or later. Additionally, review whether the internal REST API feature is required and disable it if unnecessary.
5.24.00.00 or later
- Back up current Secure Connect Gateway configuration and data according to Dell documentation
- Download the fixed version 5.24.00.00 or later from Dell support portal at dell.com
- Review Dell upgrade documentation for SCG version 5.24.00.00
- Follow the documented upgrade procedure to install version 5.24.00.00 or later
- After upgrade, verify the Internal REST API feature is properly secured and access controls are enforced
- Confirm the version installed matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28965 — 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-28965 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