Information disclosure and crash via wrong-endian follow-up length
Published Jul 9, 2021 · Updated Aug 3, 2024
Out-of-bounds read in Linux PTP Project linuxptp before 2.0.1 and 3.0 through 3.1 allows remote attackers to disclose memory or crash ptp4l. In tc_fwd_sync in tc.c, the follow-up message length is stored without conversion to network byte order, causing little-endian systems to read and transmit data beyond the message buffer. Exploitation requires network access to ptp4l operating as a transparent clock on a little-endian architecture and a crafted one-step Sync message.
Summary
What happened
Out-of-bounds read in Linux PTP Project linuxptp before 2.0.1 and 3.0 through 3.1 allows remote attackers to disclose memory or crash ptp4l. In tc_fwd_sync in tc.c, the follow-up message length is stored without conversion to network byte order, causing little-endian systems to read and transmit data beyond the message buffer. Exploitation requires network access to ptp4l operating as a transparent clock on a little-endian architecture and a crafted one-step Sync message.
The record
- CVE
- CVE-2021-3571
- Published
- Jul 9, 2021
- Updated
- Aug 3, 2024
- Vendor
- Linux PTP Project
- Product
- linuxptp
- Classifications
- CWE-119, CWE-125, T1499
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=linuxptp 3.1.1, linuxptp 2.0.1
What conditions does exploitation require?
What is affected?
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