CVE-2023-43775
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 · uneditedDenial-of-service vulnerability in the web server of the Eaton SMP Gateway allows attacker to potentially force an unexpected restart of the automation platform, impacting the availability of the product. In rare situations, the issue could cause the SMP device to restart in Safe Mode or Max Safe Mode. When in Max Safe Mode, the product is not vulnerable anymore.
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 confidenceA denial-of-service vulnerability exists in the web server component of the Eaton SMP Gateway. An attacker can exploit this to cause an unexpected restart of the automation platform, impacting system availability. In rare cases, the device may restart into Safe Mode or Max Safe Mode, with Max Safe Mode effectively mitigating the vulnerability.
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>= 8.0, < 8.0r9>= 8.1, < 8.1r5>= 8.2, < 8.2r4>= 8.0, < 8.0r9>= 8.1, < 8.1r5>= 8.2, < 8.2r4= 7.0= 7.1= 7.2>= 8.0, < 8.0r9>= 8.1, < 8.1r5>= 8.2, < 8.2r4= 6.3= 7.0= 7.1= 7.2>= 8.0, < 8.0r9= 6.3= 7.0= 7.1= 7.2CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 SMP Gateway modelLocate the product model on the device label or access the web interface to view the device information page showing the model number (SMP SG 4260, SMP SG 4250, SMP 4/dp, or SMP 16)Affected if Model is one of the four affected variants listed in the CVE
-
Check the installed firmware versionAccess the device web interface (typically https://<device-ip>/) and navigate to the System Information or About page to view the firmware version, or use the command-line interface with the appropriate show commandAffected if Version matches any of the affected ranges: 8.0 to before 8.0r9, 8.1 to before 8.1r5, 8.2 to before 8.2r4, or exact versions 6.3, 7.0, 7.1, 7.2 for the applicable model
-
Confirm the web server component is enabledAttempt to access the device web interface via HTTP or HTTPS on the standard ports (80/443), or check via CLI if web server service status is runningAffected if Web server responds and is not disabled; if the device is in Max Safe Mode, the web server will be unavailable
-
Verify Safe Mode statusCheck the device boot mode or Safe Mode setting via CLI (such as 'show system mode' or similar command) or through the web interface status pageAffected if Device is NOT running in Max Safe Mode; Max Safe Mode disables the web server and mitigates the vulnerability
The environment is affected if the device is an Eaton SMP Gateway model (SG 4260, SG 4250, 4/dp, or 16) running a vulnerable firmware version (6.3, 7.0-7.2, 8.0-8.0r8, 8.1-8.1r4, or 8.2-8.2r3) with the web server component enabled and not running in Max Safe Mode.
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 · scoped8.0r98.1r58.2r4
Until an official vendor patch is available, consider operating the device in Max Safe Mode as a workaround, as this disables the vulnerable web server component. Additionally, restrict network access to the SMP Gateway to minimize attack surface.
Upgrade to firmware 8.0r9 (for 8.0.x versions), 8.1r5 (for 8.1.x versions), or 8.2r4 (for 8.2.x versions)
- Identify the exact current firmware version of the Eaton SMP Gateway device
- For firmware 8.0.x: Upgrade to firmware version 8.0r9 or later
- For firmware 8.1.x: Upgrade to firmware version 8.1r5 or later
- For firmware 8.2.x: Upgrade to firmware version 8.2r4 or later
- For firmware 6.3, 7.0, or 7.1: Contact Eaton support for available remediation options, as no patch is listed for these older versions
- After upgrading, verify the device is operational and not in Safe Mode or Max Safe Mode
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43775 — 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-43775 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