Process crash via configuration whitespace underflow
Published Apr 8, 2022 · Updated Aug 4, 2024
Stack buffer overflow in zlog 1.2.15 allows remote attackers to crash a consuming process through crafted configuration content. In zlog_conf_build_with_file, trailing-whitespace trimming decrements a pointer before the local line buffer, reads the preceding stack byte, and can write through that invalid pointer. Network exploitation requires a consuming application to initialize zlog with attacker-controlled configuration content; the reported consequence is process termination.
Summary
What happened
Stack buffer overflow in zlog 1.2.15 allows remote attackers to crash a consuming process through crafted configuration content. In zlog_conf_build_with_file, trailing-whitespace trimming decrements a pointer before the local line buffer, reads the preceding stack byte, and can write through that invalid pointer. Network exploitation requires a consuming application to initialize zlog with attacker-controlled configuration content; the reported consequence is process termination.
The record
- CVE
- CVE-2021-43521
- Published
- Apr 8, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 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.
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