Ethernet interruption via unreleased packet resources
Published Jun 15, 2022 · Updated Jun 2, 2026
Improper resource locking in Mitsubishi Electric MELSEC and MELIPC controllers allows remote attackers to interrupt Ethernet communications. The Ethernet-port packet handler fails to release a resource after processing a specially crafted packet, exhausting the resource and halting Ethernet service. No authentication is required, and recovery requires a system reset.
Summary
What happened
Improper resource locking in Mitsubishi Electric MELSEC and MELIPC controllers allows remote attackers to interrupt Ethernet communications. The Ethernet-port packet handler fails to release a resource after processing a specially crafted packet, exhausting the resource and halting Ethernet service. No authentication is required, and recovery requires a system reset.
The record
- CVE
- CVE-2022-24946
- Published
- Jun 15, 2022
- Updated
- Jun 2, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-667, CWE-413, T0814
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2022CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo