# CVE-2022-41404: org.ini4j allows attackers to cause a Denial of Service (DoS)

> Attackers can cause a Denial of Service in the ini4j library via the fetch method in BasicProfile, affecting Java applications using this dependency.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Oct 2022
- **Updated:** 9 Jun 2025
- **Also known as:** DEBIAN-CVE-2022-41404, DLA-3209-1, GHSA-jr6h-r7vg-f9mc, UBUNTU-CVE-2022-41404, openSUSE-SU-2024:13788-1

## What is CVE-2022-41404?

CVE-2022-41404 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the fetch() method in the BasicProfile class of org.ini4j through version v0.5.4 allows attackers to cause a Denial of Service (DoS) via unspecified vectors.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-41404?

2 open source packages ship an affected version, including org.ini4j:ini4j. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.ini4j:ini4j` | Maven | All versions to 0.5.4 | None |
| `org.ini4j:ini4j` | Maven | All versions to 0.5.4 | None |
| `ini4j` | openSUSE:Tumbleweed | All versions | 0.5.4-1.1 |

Products: Debian Debian Linux, Ini4j Project Ini4j.

## How do I fix CVE-2022-41404?

Upgrade to a fixed version.

## Is CVE-2022-41404 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41404 exists.

Public exploit code:

- Windows Apache Tomcat resource limits implementation guide for CVE-2022-41404 DoS vulnerability protection (github_poc): https://github.com/fdjy1234/CVE-2022-41404-DoS-Protection

## 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-2022-41404 and fix it if it is affected.

What it is: CVE-2022-41404 is a high-severity denial of service vulnerability in Debian Debian Linux, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41404 exists.

Affected packages and fixed versions:
- org.ini4j:ini4j (Maven): affected all versions up to 0.5.4; no fix listed
- org.ini4j:ini4j (Maven): affected all versions up to 0.5.4; no fix listed

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-2022-41404/ (Markdown: https://insights.sbomify.com/CVE-2022-41404/index.md)
```

## Sources

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

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