OpenPLC v3 ud2 Instruction enipThread reliance on undefined, unspecified, or implementation-defined behavior
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in OpenPLC v3. Impacted is the function enipThread of the component ud2 Instruction Handler. Performing a manipulation results in reliance on undefined, unspecified, or implementation-defined behavior.
This vulnerability was named CVE-2025-54811. The attack needs to be approached locally. There is no available exploit.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability was found in OpenPLC v3 (the affected version is unknown). It has been classified as problematic. This affects the function enipThread of the component ud2 Instruction Handler. The manipulation with an unknown input leads to a reliance on undefined, unspecified, or implementation-defined behavior vulnerability. CWE is classifying the issue as CWE-758. The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity. This is going to have an impact on availability. The summary by CVE is:
OpenPLC_V3 has a vulnerability in the enipThread function that occurs due to the lack of a return value. This leads to a crash when the server loop ends and execution hits an illegal ud2 instruction. This issue can be triggered remotely without authentication by starting the same server multiple times or if the server exits unexpectedly. The vulnerability allows an attacker to cause a Denial of Service (DoS) against the PLC runtime, stopping any PC started remotely without authentication. This results in the PLC process crashing and halting all automation or control logic managed by OpenPLC.
It is possible to read the advisory at cisa.gov. This vulnerability is uniquely identified as CVE-2025-54811. The exploitability is told to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.
Applying a patch is able to eliminate this problem.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Reliance on undefined, unspecified, or implementation-defined behaviorCWE: CWE-758
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
10/01/2025 Advisory disclosed10/01/2025 VulDB entry created
10/02/2025 VulDB entry last update
Sources
Advisory: icsa-25-273-05Status: Confirmed
CVE: CVE-2025-54811 (🔒)
GCVE (CVE): GCVE-0-2025-54811
GCVE (VulDB): GCVE-100-326463
Entry
Created: 10/01/2025 09:48Updated: 10/02/2025 12:19
Changes: 10/01/2025 09:48 (50), 10/02/2025 12:19 (24)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.