Memory disclosure via chained pbuf over-read
Published Jul 22, 2021 · Updated Aug 4, 2024
Buffer over-read in lwIP 2.1.2 allows remote attackers to access sensitive memory via a crafted 6LoWPAN packet. In zepif_linkoutput(), pbuf_take_at() copies p->tot_len bytes from the first chained pbuf payload even though that buffer contains only p->len bytes. The affected ZEP output path must process a chained packet, after which adjacent memory is included in the UDP broadcast without authentication or user interaction.
Summary
What happened
Buffer over-read in lwIP 2.1.2 allows remote attackers to access sensitive memory via a crafted 6LoWPAN packet. In zepif_linkoutput(), pbuf_take_at() copies p->tot_len bytes from the first chained pbuf payload even though that buffer contains only p->len bytes. The affected ZEP output path must process a chained packet, after which adjacent memory is included in the UDP broadcast without authentication or user interaction.
The record
- CVE
- CVE-2020-22284
- Published
- Jul 22, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 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.
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