dbcve.org
Secure Connect GatewayApplication · Dell

CVE-2023-44293

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-14
Fix available
A fix is available. Upgrade to 5.20.00.00 or later.
See remediation →
71/100
Remediation priority · Elevated
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
In Dell Secure Connect Gateway Application and Secure Connect Gateway Appliance (between v5.10.00.00 and v5.18.00.00), a security concern has been identified, where a malicious user with a valid User session may inject malicious content in filters of IP Range Rest API. This issue may potentially lead to unintentional information disclosure from the product database.

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 confidence

Authenticated users with valid sessions can inject malicious content into filters of the IP Range Rest API in Dell Secure Connect Gateway versions 5.10.00.00 through 5.18.00.00. This input validation failure in the API filter parameter allows injection attacks that can lead to unintended database information disclosure.

MitigationApply vendor patch or upgrade to a version beyond v5.18.00.00; alternatively, implement proper input validation and parameterized queries in the IP Range Rest API filter handling code.

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.10.00.00, < 5.20.00.00

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Check installed Dell Secure Connect Gateway version
    Access the system management interface or run 'show version' command via CLI to retrieve the current firmware/software version
    Affected if Version is 5.10.00.00 through 5.18.00.00 (inclusive)
  2. Confirm version is within affected range
    Compare the installed version against the vulnerable range: versions >= 5.10.00.00 and < 5.20.00.00 are affected
    Affected if Installed version falls between 5.10.00.00 and 5.18.00.00 inclusive
  3. Verify IP Range Rest API is accessible
    Check if the IP Range Rest API endpoint is exposed and accessible in the environment (typically at /api/ip-range or similar path)
    Affected if IP Range Rest API is enabled and reachable on the system
  4. Check for authenticated user sessions
    Review active session configurations and user authentication settings for the API
    Affected if Authenticated user sessions exist or can be created for API access

System is affected if Dell Secure Connect Gateway version is 5.10.00.00 through 5.18.00.00 AND the IP Range Rest API is accessible to authenticated users.

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 5.20.00.00 or later
Fixed in 5.20.00.00
Interim mitigation

Apply vendor patch or upgrade to a version beyond v5.18.00.00; alternatively, implement proper input validation and parameterized queries in the IP Range Rest API filter handling code.

Recommended fix High confidence

Secure Connect Gateway version 5.20.00.00 or later

  1. 1. Back up the current Secure Connect Gateway configuration and any critical data.
  2. 2. Schedule a maintenance window for the upgrade process.
  3. 3. Download Secure Connect Gateway version 5.20.00.00 or later from the Dell support portal.
  4. 4. Follow the official Dell upgrade documentation for Secure Connect Gateway to apply the update.
  5. 5. After upgrade, verify the IP Range Rest API functionality is working correctly.
  6. 6. Confirm the upgrade was successful by checking the product version in the admin interface.
Caveat Review Dell release notes for 5.20.00.00 for any configuration or behavioral changes that may affect existing integrations

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44293 — 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-2023-44293 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