Misdirected writes via erroneous descriptor zero closure
Published Jan 1, 2022 · Updated Aug 4, 2024
Resource management flaw in Go before 1.16.12 and 1.17.0 through 1.17.4 allows remote attackers to misdirect file or network writes. On UNIX, syscall.ForkExec treats zero-initialized pipe descriptor slots as valid after pipe creation fails and closes file descriptor 0. Exploitation requires exhausting a process's descriptors and repeatedly triggering ForkExec, directly or through os/exec, causing cross-file or cross-connection I/O.
Summary
What happened
Resource management flaw in Go before 1.16.12 and 1.17.0 through 1.17.4 allows remote attackers to misdirect file or network writes. On UNIX, syscall.ForkExec treats zero-initialized pipe descriptor slots as valid after pipe creation fails and closes file descriptor 0. Exploitation requires exhausting a process's descriptors and repeatedly triggering ForkExec, directly or through os/exec, causing cross-file or cross-connection I/O.
The record
- CVE
- CVE-2021-44717
- Published
- Jan 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-404
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 1, 2022CVE 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