# CVE-2019-25667: TaskInfo 8.2.0.280 Denial of Service Buffer Overflow

> Attackers can crash the TaskInfo application by entering oversized strings into registration fields, causing a denial of service.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-cgqv-mm6v-7jj7

## What is CVE-2019-25667?

CVE-2019-25667 is a medium-severity memory corruption vulnerability in Iarsn TaskInfo, published on 5 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TaskInfo 8.2.0.280 contains a local buffer overflow vulnerability that allows attackers to crash the application by supplying oversized input to registration fields. Attackers can paste excessively long strings into the New User Name or New Serial Number textboxes in the Help menu's registration dialog to trigger a denial of service condition.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Iarsn Taskinfo.

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

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

## Is CVE-2019-25667 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25667 is a medium-severity memory corruption vulnerability in Iarsn TaskInfo, published on 5 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25667 exists.

Affected product: Iarsn TaskInfo. 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-25667/ (Markdown: https://insights.sbomify.com/CVE-2019-25667/index.md)
```

## Sources

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

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