# CVE-2025-0633: Heap Overflow in iniparser.c

> A heap-based buffer overflow in the iniparser library allows attackers to read out-of-bounds memory, potentially leading to information disclosure or crashes.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 19 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** AZL-56943, AZL-57019, DEBIAN-CVE-2025-0633, ECHO-5d31-188a-5e5c, GHSA-2599-v2c2-3fp3, MGASA-2025-0077, OESA-2025-1277, SUSE-SU-2025:0821-1, SUSE-SU-2025:0845-1, UBUNTU-CVE-2025-0633, USN-7286-1, openSUSE-SU-2025:14836-1

## What is CVE-2025-0633?

CVE-2025-0633 is a medium-severity memory corruption vulnerability in iniparser, published on 19 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based Buffer Overflow vulnerability in iniparser_dumpsection_ini() in iniparser allows attacker to read out of bound memory

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-0633?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `iniparser` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 4.1-150500.4.8.1 |
| `iniparser` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.1.0.git20140619_c5beb80a-3.6.1 |
| `iniparser` | openSUSE:Leap 15.6 | All versions | 4.1-150500.4.8.1 |
| `iniparser` | openSUSE:Tumbleweed | All versions | 4.2.6-1.1 |

## How do I fix CVE-2025-0633?

Apply the vendor's patch.

## Is CVE-2025-0633 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0633 and fix it if it is affected.

What it is: CVE-2025-0633 is a medium-severity memory corruption vulnerability in iniparser, published on 19 Feb 2025. 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-2025-0633 in the wild and no public exploit code.

Affected product: iniparser. 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-2025-0633/ (Markdown: https://insights.sbomify.com/CVE-2025-0633/index.md)
```

## Sources

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

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