CVE-2023-44294
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 · uneditedIn 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 Collection 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 confidenceThis is an injection vulnerability in Dell Secure Connect Gateway where an authenticated user can inject malicious content into the filters of the Collection Rest API. The vulnerable component is the API's filter parameter handling, which lacks proper input sanitization. A user with valid credentials can craft malicious filter queries that allow unintended database information disclosure.
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.10.00.00, < 5.20.00.00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Dell Secure Connect Gateway installationLocate the Dell Secure Connect Gateway application on the system. Check the product version by accessing the administration interface or checking the installed software package. Common paths include the product's web UI or command line interface using 'scg-version' or similar utility if available.Affected if The product is Dell Secure Connect Gateway with a version between 5.10.00.00 and 5.19.00.00 inclusive.
-
Verify installed version against affected rangeCompare your installed version number to the affected range: version 5.10.00.00 or higher but lower than 5.20.00.00. This can be done via the product's web UI under 'About' or 'System Information', or via CLI if accessible.Affected if The installed version falls within >= 5.10.00.00 and < 5.20.00.00.
-
Confirm Collection Rest API accessibilityDetermine if the Collection Rest API endpoint is exposed and accessible. Check the API documentation or system configuration to identify if endpoints such as /api/v1/collections or similar filter-based endpoints are enabled. This can be verified through network configuration or API gateway settings.Affected if The Collection Rest API is exposed and accepts filter parameters without additional authentication beyond basic user credentials.
-
Review API access logs for suspicious filter queriesExamine application and API logs for unusual or malformed filter query patterns in Collection Rest API calls. Look for filter parameters containing SQL-like syntax, unexpected characters, or queries that appear to probe database structure. Log locations typically include /var/log/scga or product-specific log directories accessible via the administration interface.Affected if Logs contain filter queries with injection-like patterns from any authenticated user, especially those that return unexpected data or trigger errors.
You are affected if Dell Secure Connect Gateway version 5.10.00.00 through 5.19.00.00 is installed and the Collection Rest API is accessible to authenticated users.
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.20.00.00
Upgrade to Dell Secure Connect Gateway v5.18.00.00 or later, which contains the security fix. Until then, restrict API access to only trusted users and monitor for suspicious query patterns in the Collection Rest API.
5.20.00.00 or later
- 1. Back up the current Secure Connect Gateway configuration and database.
- 2. Schedule a maintenance window for the upgrade process.
- 3. Download Secure Connect Gateway version 5.20.00.00 or later from Dell support portal (support.dell.com).
- 4. Follow Dell's documented upgrade procedure for Secure Connect Gateway Appliance.
- 5. Verify the upgrade was successful by logging into the management console.
- 6. Confirm the Collection Rest API filters are functioning correctly.
- 7. Validate that the previously reported vulnerability is no longer present.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-44294 — 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-2023-44294 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