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

> Remote attackers can cause a denial of service in dtSearch via a crafted HTTP request exploiting stack exhaustion in the search function.

- **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:** 29 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-22hx-9864-2fvh

## What is CVE-2018-11488?

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

### Official description

A stack exhaustion vulnerability in the search function of dtSearch 7.90.8538.1 and prior allows remote attackers to cause a denial of service condition by sending a specially crafted HTTP request.

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

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

It affects 1 product.


Products: Dtsearch Dtsearch.

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

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

## Is CVE-2018-11488 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-8088](https://insights.sbomify.com/CVE-2025-8088/): RARLAB WinRAR Path Traversal (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11488 is a high-severity denial of service vulnerability in n/a, published on 29 May 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-11488 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-11488/ (Markdown: https://insights.sbomify.com/CVE-2018-11488/index.md)
```

## Sources

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

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