CVE-2023-28043
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 5.14 contains an information disclosure vulnerability during the SRS to SCG upgrade path. A remote low privileged malicious user could potentially exploit this vulnerability to retrieve the plain text.
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 Secure Connectivity Gateway (SCG) 5.14 contains an information disclosure vulnerability in the upgrade path from SRS (presumably Secure Remote Services) to SCG. A remote, low-privileged authenticated attacker could exploit this vulnerability to retrieve plaintext sensitive data during the upgrade process, likely due to improper handling or encryption of credentials/configuration data in the migration workflow.
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.14.00.16CVSS 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.
-
Verify the installed Dell Secure Connect Gateway versionAccess the SCG administrative interface or run the command to display the product version (typically available in the system information or about section of the web UI, or via CLI command like 'show version' or 'system show version')Affected if The installed version is exactly 5.14.00.16
-
Confirm the product is Dell Secure Connect GatewayVerify the product name in the system information or administrative interface matches 'Dell Secure Connect Gateway' or 'Dell Secure Connectivity Gateway' (SCG)Affected if The product is Dell Secure Connect Gateway version 5.14.00.16
-
Determine if an upgrade from SRS to SCG is present or has been performedCheck the system configuration or logs for evidence of SRS (Secure Remote Services) to SCG migration artifacts, upgrade history, or migration configuration filesAffected if The system shows evidence of an SRS to SCG upgrade path and the version is 5.14.00.16
-
Check for sensitive data exposure in upgrade migration filesInspect any temporary migration files, backup files, or configuration dumps in the upgrade or migration directory (locations may include /opt, /tmp, or application data directories) for plaintext credentials or sensitive configuration dataAffected if Plaintext sensitive data is found in upgrade-related files and the version is 5.14.00.16
The environment is affected only if Dell Secure Connect Gateway version 5.14.00.16 is installed and an SRS to SCG upgrade path exists or has been performed.
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.
From vendor dataApply the vendor patch or update to SCG beyond version 5.14. If immediate patching is not feasible, restrict network access to the upgrade interface and ensure low-privilege accounts do not have access to upgrade-related functionality until the patch is applied.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28043 — 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-28043 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