Kernel code execution via unchecked MSG_CRYPTO key length
Published Nov 2, 2021 · Updated Aug 4, 2024
Heap buffer overflow in Linux kernel TIPC before 5.14.16 allows remote attackers to execute code via crafted MSG_CRYPTO packets. tipc_crypto_key_rcv allocates memory from the message payload size, then copies attacker-controlled keylen bytes before validating that the key fits the allocation. TIPC must be loaded and configured on Ethernet or UDP; successful exploitation runs code with kernel privileges and can fully compromise the host.
Summary
What happened
Heap buffer overflow in Linux kernel TIPC before 5.14.16 allows remote attackers to execute code via crafted MSG_CRYPTO packets. tipc_crypto_key_rcv allocates memory from the message payload size, then copies attacker-controlled keylen bytes before validating that the key fits the allocation. TIPC must be loaded and configured on Ethernet or UDP; successful exploitation runs code with kernel privileges and can fully compromise the host.
The record
- CVE
- CVE-2021-43267
- Published
- Nov 2, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1284, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 2, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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