CVE-2023-5459
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 · uneditedA vulnerability has been found in Delta Electronics DVP32ES2 PLC 1.48 and classified as critical. This vulnerability affects unknown code of the component Password Transmission Handler. The manipulation leads to denial of service. The exploit has been disclosed to the public and may be used. VDB-241582 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
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 vulnerability in the password transmission handler component of Delta Electronics DVP32ES2 PLC version 1.48 allows remote attackers to cause denial of service. The exploit has been publicly disclosed, and the vendor did not respond to early disclosure attempts, indicating no official patch is available.
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= 1.48= 1.48= 1.48= 1.48= 1.48= 1.48= 1.48CVSS 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.
-
Identify the PLC modelLocate the physical PLC unit or check network inventory for Delta Electronics DVP32ES2 series devices. The model number (e.g., DVP32ES200R, DVP32ES200T, DVP32ES211T, DVP32ES200RC, DVP32ES200TC, DVP32ES200RE, DVP32ES200TE) should be visible on the device label or obtainable via network scanning tools that identify industrial devices.Affected if The device is any of the following models: Dvp32es200r, Dvp32es200t, Dvp32es211t, Dvp32es200rc, Dvp32es200tc, Dvp32es200re, or Dvp32es200te.
-
Check the firmware versionAccess the PLC via Delta WPLSoft or ISPSoft programming software, or check via the device web interface if available, to determine the installed firmware version. The version is typically found in the system information or device properties section.Affected if The firmware version is exactly 1.48.
-
Verify password transmission handler configurationExamine the PLC project file (.dvp file) or the device configuration for any password-related settings, particularly those involving transmission or communication of passwords to external systems. Check if password protection is enabled for ladder logic, function block access, or device communication.Affected if Password transmission or password communication features are enabled or configured on the device.
-
Assess network exposureReview network firewall rules, segment boundaries, and access control lists to determine if the PLC is accessible from untrusted networks. Check for direct internet exposure or accessibility from corporate networks rather than isolated operational technology networks.Affected if The PLC is reachable from network segments that are not strictly controlled or are exposed to unauthorized access.
A user is affected if they have a Delta DVP32ES2 series PLC (any of the seven listed models) running firmware version 1.48 with password transmission features enabled and accessible from an untrusted network.
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 · scopedImplement network segmentation and firewall controls to restrict unauthorized access to the PLC, and monitor for signs of exploitation given the publicly available exploit and lack of vendor-provided patch.
- Implement network segmentation to isolate the affected PLCs from untrusted networks
- Place the DVP32ES2 devices behind a firewall or industrial DMZ
- Restrict network access to the PLCs using IP whitelisting and allowlists
- Disable or restrict remote access to the Password Transmission Handler if possible
- Monitor network traffic for signs of the denial of service exploit
- Implement compensating controls such as intrusion detection/prevention systems (IDS/IPS) on the industrial network
- Ensure robust backup and recovery procedures are in place to restore PLC functionality after a DoS incident
- Consider reaching out directly to Delta Electronics through alternative channels (regional offices, industrial system integrators) to escalate the lack of vendor response
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-5459 — 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-5459 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