CVE-2024-46613
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWeeChat before 4.4.2 has an integer overflow and resultant buffer overflow at core/core-string.c when there are more than two billion items in a list. This affects string_free_split_shared , string_free_split, string_free_split_command, and string_free_split_tags.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWeeChat before 4.4.2 contains an integer overflow vulnerability in core/core-string.c. When processing lists with more than 2 billion items, the item counter overflows, causing memory allocation functions (string_free_split_shared, string_free_split, string_free_split_command, string_free_split_tags) to allocate insufficient buffer space, leading to a heap-based buffer overflow that could enable remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 0.1.6, < 4.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WeeChat versionRun `weechat --version` or check the version through the WeeChat interface with `/script` command and look at the WeeChat version displayedAffected if Version is 0.1.6 or higher but lower than 4.4.2
-
Confirm integer overflow conditionThis vulnerability triggers when string split functions process lists containing more than 2,147,483,647 (2 billion) itemsAffected if Your WeeChat instance processes lists exceeding 2 billion items in string split operations
You are affected if your WeeChat version is 0.1.6 or higher but lower than 4.4.2 and you process lists with more than 2 billion items in string split operations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped4.4.2
Upgrade WeeChat to version 4.4.2 or later. Until upgrade is possible, consider limiting or validating the number of items processed in string split operations to stay below the 2 billion threshold.
WeeChat 4.4.2
- Check current WeeChat version by running `weechat --version` or typing `/version` in WeeChat
- If version is less than 4.4.2, upgrade to WeeChat 4.4.2 or later
- For Linux distributions using package managers: run `apt-get update && apt-get install weechat` (Debian/Ubuntu), `dnf update weechat` (Fedora/RHEL), or `pacman -Syu weechat` (Arch)
- For source compilation: download WeeChat 4.4.2 from weechat.org or GitHub releases, then compile and install
- After upgrading, restart WeeChat
- Confirm the new version is 4.4.2 or later using `/version`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46613 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46613 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data