dbcve.org
Secure Connect GatewayApplication · Dell

CVE-2024-29168

HIGH · 8.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to after 5.22.00.18 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Dell SCG, versions prior to 5.22.00.00, contain a SQL Injection Vulnerability in the SCG UI for an internal assets REST API. A remote authenticated attacker could potentially exploit this vulnerability, leading to the execution of certain SQL commands on the application's backend database causing potential unauthorized access and modification of application data.

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 · high confidence

Dell Secure Connect Gateway (SCG) versions prior to 5.22.00.00 contain a SQL injection vulnerability in the SCG UI's internal assets REST API. A remote authenticated attacker can inject malicious SQL commands through this API endpoint, potentially reading, modifying, or deleting data in the application's backend database.

MitigationUpgrade Dell SCG to version 5.22.00.00 or later to obtain the vendor patch. Apply least-privilege principles to API user accounts and monitor database activity for anomalous queries until the upgrade is completed.

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
Secure Connect GatewayApplication
Affected:>= 5.18.00.20, <= 5.22.00.18

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check the installed Dell SCG version
    Log into the SCG admin console and navigate to the 'About' or 'System Information' page to view the installed version. Alternatively, check via CLI if available: /opt/dell/scg/bin/scgadmin --version or look for version files in /opt/dell/scg/
    Affected if The version is 5.18.00.20 or higher but lower than 5.22.00.00 (the fix was released in 5.22.00.00)
  2. Verify the internal assets REST API is accessible
    Attempt to access the internal assets REST API endpoint. The typical path is /scg-ui/api/v1/assets or similar under the SCG UI base URL. Use a web browser or curl to test unauthenticated vs authenticated access.
    Affected if The REST API endpoint is reachable from the network without being explicitly disabled or firewalled
  3. Confirm authentication is possible on the SCG UI
    Attempt to log into the SCG admin console with a valid user account. The vulnerability requires an authenticated session to exploit the SQL injection.
    Affected if Valid user credentials exist or can be obtained for the SCG application (even low-privilege accounts can trigger this flaw)
  4. Review SCG audit and database logs for anomalous SQL
    Examine SCG logs in /opt/dell/scg/logs/ for unusual database queries, especially those containing SQL operators like UNION, SELECT, DROP, or INSERT in the request parameters. Check database audit logs if accessible.
    Affected if Logs show unexpected SQL-like patterns in API request parameters or unusual database queries originating from the SCG UI layer

Your environment is affected if the installed Dell SCG version falls between 5.18.00.20 and 5.22.00.18 inclusive, the internal assets REST API is network-accessible, and an attacker can obtain valid SCG credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 5.22.00.18
Interim mitigation

Upgrade Dell SCG to version 5.22.00.00 or later to obtain the vendor patch. Apply least-privilege principles to API user accounts and monitor database activity for anomalous queries until the upgrade is completed.

Recommended fix High confidence

Dell Secure Connect Gateway 5.22.00.00 or later

  1. 1. Identify the current installed version of Dell Secure Connect Gateway (SCG) in your environment
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Back up the current SCG configuration and any critical data
  4. 4. Download Dell Secure Connect Gateway version 5.22.00.00 or later from the Dell Support website (www.dell.com/support)
  5. 5. Follow Dell's documented upgrade procedure for SCG, applying the upgrade package to all SCG instances in your deployment
  6. 6. Verify the upgrade completed successfully by checking the version in the SCG admin console
  7. 7. Confirm the SQL injection vulnerability is resolved by verifying the internal assets REST API now properly sanitizes database queries
  8. 8. Test that legitimate SCG functionality continues to work as expected after the upgrade
Caveat Standard upgrade risks apply - ensure backups before proceeding and test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secure Connect Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29168 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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