Alarm receiver stops delivering alarms after a malformed alarm notification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| RT-Labs | P-Net | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rt-labs | P-net |
|
Vendor Solution
Upgrade to P-Net 1.0.4 or later.
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rt-labs
Rt-labs p-net |
|
| Vendors & Products |
Rt-labs
Rt-labs p-net |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | P-Net before 1.0.4 sets the alarm receiver state to waiting for confirmation before the data of a received alarm notification is parsed. If the parsing fails the state is not restored, and later alarm notifications of the same priority are discarded without acknowledge until the Application Relationship is released. The Application Relationship and the cyclic data exchange keep working. The attacker must be able to send an alarm notification in the context of an established Application Relationship and requires ADJACENT network access. | |
| Title | Alarm receiver stops delivering alarms after a malformed alarm notification | |
| Weaknesses | CWE-754 | |
| References |
| |
| Metrics |
cvssV4_0
|
Improper Check for Unusual or Exceptional Conditions