# CVE-2019-25341: iNetTools for iOS 8.20 - 'Whois' Denial of Service

> Attackers can crash the iNetTools iOS application by pasting a specially crafted buffer into the Whois Domain Name field.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:H/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-ggf8-hhhc-6pgc

## What is CVE-2019-25341?

CVE-2019-25341 is a medium-severity denial of service vulnerability in iNetTools for iOS, published on 12 Feb 2026. 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

iNetTools for iOS 8.20 contains a denial of service vulnerability in the Whois feature that allows attackers to crash the application by manipulating input. Attackers can paste a specially crafted 98-character buffer into the Domain Name field to trigger an application crash.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2019-25341?


## How do I fix CVE-2019-25341?

No fix has been published for CVE-2019-25341 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-25341 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25341 and fix it if it is affected.

What it is: CVE-2019-25341 is a medium-severity denial of service vulnerability in iNetTools for iOS, published on 12 Feb 2026. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25341 exists.

Affected product: iNetTools for iOS. 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-2019-25341/ (Markdown: https://insights.sbomify.com/CVE-2019-25341/index.md)
```

## Sources

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

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