CVE-2023-2263
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 · uneditedThe Rockwell Automation Kinetix 5700 DC Bus Power Supply Series A is vulnerable to CIP fuzzing. The new ENIP connections cannot be established if impacted by this vulnerability, which prohibits operational capabilities of the device resulting in a denial-of-service attack.
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 confidenceThe Rockwell Automation Kinetix 5700 DC Bus Power Supply Series A contains a vulnerability susceptible to CIP fuzzing. This vulnerability prevents new ENIP (EtherNet/IP) connections from being established, effectively causing a denial-of-service condition that blocks operational communication with the device.
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= 13.001CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the device modelAccess the device through its web interface, Rockwell Studio 5000, or RSLinx Classic to identify the exact hardware model. Look for 'Kinetix 5700 DC Bus Power Supply Series A' in the device hierarchy or device properties.Affected if The device is not a Kinetix 5700 DC Bus Power Supply Series A
-
Check the installed firmware versionIn RSLinx Classic, right-click the device and select 'Device Properties' to view firmware version. Alternatively, use the device's built-in web interface under 'Device Status' or 'Properties'. Compare the firmware version shown to 13.001.Affected if The firmware version is exactly 13.001
-
Verify ENIP communication is enabledCheck the device configuration in Studio 5000 Logix Designer or the device web interface for EtherNet/IP adapter settings. Look for ENIP (EtherNet/IP) communication module status and ensure it is configured as an adapter or scanner.Affected if ENIP communication is enabled and the device is configured to accept ENIP connections
-
Confirm the device accepts ENIP connectionsUse RSLinx Classic or a network scanner to verify the device is responding to ENIP CIP requests. Attempt to establish an ENIP session or check the connection status in RSLinx.Affected if The device accepts and processes ENIP connections
The environment is affected if the device is a Kinetix 5700 DC Bus Power Supply Series A running firmware version 13.001 with ENIP communication enabled and actively accepting connections.
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 vendor-supplied patches or firmware updates when available; implement network segmentation and ENIP connection rate limiting to reduce attack surface; monitor for anomalous connection patterns.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2263 — 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-2263 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