# CVE-1999-1030: Denial of service in n/a

> Remote attackers can crash the counter.exe web server by sending a malformed HTTP request ending in a newline character.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2001
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-m3vx-4vqh-h434

## What is CVE-1999-1030?

CVE-1999-1030 is a medium-severity denial of service vulnerability in n/a, published on 12 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

counter.exe 2.70 allows a remote attacker to cause a denial of service (hang) via an HTTP request that ends in %0A (newline), which causes a malformed entry in the counter log that produces an access violation.

## Which versions are affected by CVE-1999-1030?

It affects 1 product.


Products: Behold Software Web Page Counter.

## How do I fix CVE-1999-1030?

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

## Is CVE-1999-1030 being exploited?

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

Public exploit code:

- Behold! Software Web Page Counter 2.7 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-1999-1031](https://insights.sbomify.com/CVE-1999-1031/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-1030 and fix it if it is affected.

What it is: CVE-1999-1030 is a medium-severity denial of service vulnerability in n/a, published on 12 Sep 2001. 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-1999-1030 exists.

Affected product: n/a. 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-1999-1030/ (Markdown: https://insights.sbomify.com/CVE-1999-1030/index.md)
```

## Sources

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

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