# CVE-2018-25423: Arm Whois 3.11 Denial of Service via Buffer Overflow

> Local attackers can crash the Arm Whois application by supplying oversized input strings, 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:** 30 May 2026
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-mv86-8f26-gw3x

## What is CVE-2018-25423?

CVE-2018-25423 is a medium-severity memory corruption vulnerability in Armcode Arm Whois, published on 30 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Arm Whois 3.11 contains a buffer overflow vulnerability that allows local attackers to crash the application by supplying an oversized input string. Attackers can paste a malicious buffer of 700 bytes into the IP address or domain input field to trigger a denial of service condition.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2018-25423?


## How do I fix CVE-2018-25423?

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

## Is CVE-2018-25423 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25423 and fix it if it is affected.

What it is: CVE-2018-25423 is a medium-severity memory corruption vulnerability in Armcode Arm Whois, published on 30 May 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-2018-25423 exists.

Affected product: Armcode Arm Whois. 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-2018-25423/ (Markdown: https://insights.sbomify.com/CVE-2018-25423/index.md)
```

## Sources

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

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