# CVE-2023-33204: Integer overflow in n/a

> An integer overflow in sysstat can lead to denial of service, affecting Linux distributions using this monitoring tool.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 May 2023
- **Updated:** 3 Nov 2025
- **Also known as:** ALSA-2023:6569, ALSA-2023:7010, AZL-26784, BELL-CVE-2023-33204, DEBIAN-CVE-2023-33204, DLA-3434-1, GHSA-57g7-qvg2-m23f, MGASA-2023-0203, OESA-2023-1301, RHSA-2023:6569, RHSA-2023:7010, UBUNTU-CVE-2023-33204, openSUSE-SU-2024:12961-1

## What is CVE-2023-33204?

CVE-2023-33204 is a high-severity vulnerability in Debian Debian Linux, published on 18 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

sysstat through 12.7.2 allows a multiplication integer overflow in check_overflow in common.c. NOTE: this issue exists because of an incomplete fix for CVE-2022-39377.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2023-33204?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sysstat` | AlmaLinux:8 | All versions | 11.7.3-11.el8 |
| `sysstat` | AlmaLinux:9 | All versions | 12.5.4-7.el9 |
| `sysstat` | Red Hat:enterprise_linux:8::appstream | All versions | 0:11.7.3-11.el8 |
| `sysstat-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:11.7.3-11.el8 |
| `sysstat-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:11.7.3-11.el8 |
| `sysstat` | Red Hat:enterprise_linux:9::appstream | All versions | 0:12.5.4-7.el9 |
| `sysstat-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:12.5.4-7.el9 |
| `sysstat-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:12.5.4-7.el9 |
| `sysstat` | openSUSE:Tumbleweed | All versions | 12.6.2-2.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Sysstat Project Sysstat.

## How do I fix CVE-2023-33204?

Apply the vendor's patch.

## Is CVE-2023-33204 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33204 and fix it if it is affected.

What it is: CVE-2023-33204 is a high-severity vulnerability in Debian Debian Linux, published on 18 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-33204 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2023-33204/ (Markdown: https://insights.sbomify.com/CVE-2023-33204/index.md)
```

## Sources

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

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