# CVE-2018-7582: Denial of service in n/a

> Remote attackers can crash the WebLog Expert Web Server Enterprise daemon by sending a long HTTP Accept Header to port 9991.

- **Severity:** High 7.5 (`CVSS:3.0/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:** No
- **Published:** 9 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xpmg-2q9q-ch22

## What is CVE-2018-7582?

CVE-2018-7582 is a high-severity denial of service vulnerability in n/a, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WebLog Expert Web Server Enterprise 9.4 allows Remote Denial Of Service (daemon crash) via a long HTTP Accept Header to TCP port 9991.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Weblogexpert Weblog Expert.

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

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

## Is CVE-2018-7582 being exploited?

There is no known exploitation of CVE-2018-7582 in the wild and no public exploit code.

Public exploit code:

- WebLog Expert Enterprise 9.4 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2018-7581](https://insights.sbomify.com/CVE-2018-7581/): Misconfiguration in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7582 is a high-severity denial of service vulnerability in n/a, published on 9 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7582 in the wild and no public exploit code.

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

## Sources

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

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