Memory corruption via overflowing split-list indexes
Published Nov 10, 2024 · Updated Nov 19, 2024
Integer overflow in WeeChat 0.1.6 through 4.4.1 allows attackers to corrupt memory when freeing a list with over 2,147,483,647 items. The affected string_free_split routines advance signed integer indexes through null-terminated pointer arrays; after INT_MAX, the indexes wrap and address elements outside the arrays. Triggering the flaw requires an extraordinarily large in-process list, and the vendor bounds the result to low confidentiality, integrity, and availability impact.
Summary
What happened
Integer overflow in WeeChat 0.1.6 through 4.4.1 allows attackers to corrupt memory when freeing a list with over 2,147,483,647 items. The affected string_free_split routines advance signed integer indexes through null-terminated pointer arrays; after INT_MAX, the indexes wrap and address elements outside the arrays. Triggering the flaw requires an extraordinarily large in-process list, and the vendor bounds the result to low confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2024-46613
- Published
- Nov 10, 2024
- Updated
- Nov 19, 2024
- Vendor
- WeeChat
- Product
- WeeChat
- Classifications
- CWE-190
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 10, 2024CVE publishedPublication date reported by the CVE source.
- Nov 19, 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=0 <4.4.2
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