# CVE-2024-46613: Integer overflow in n/a

> An integer overflow in WeeChat can lead to a buffer overflow, potentially allowing code execution or denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-46613, GHSA-q743-h9vw-38hv, UBUNTU-CVE-2024-46613, openSUSE-SU-2025:14734-1

## What is CVE-2024-46613?

CVE-2024-46613 is a medium-severity vulnerability in n/a, published on 10 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WeeChat 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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2024-46613?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `weechat` | openSUSE:Tumbleweed | All versions | 4.5.1-1.1 |

Products: Weechat Weechat.

## How do I fix CVE-2024-46613?

Upgrade to a fixed version.

## Is CVE-2024-46613 being exploited?

There is no known exploitation of CVE-2024-46613 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-28352](https://insights.sbomify.com/CVE-2022-28352/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-46613 and fix it if it is affected.

What it is: CVE-2024-46613 is a medium-severity vulnerability in n/a, published on 10 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-46613 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-46613/ (Markdown: https://insights.sbomify.com/CVE-2024-46613/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-46613
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-46613
- OSV: https://osv.dev/vulnerability/CVE-2024-46613

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-46613/
Summaries are generated and may contain mistakes; the official description above is the record.