# CVE-2018-3767: Denial of Service in memjs

> An attacker can cause a denial of service and uninitialized memory usage in the memjs library by sending typed input.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 5 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cx8m-8xmx-q8v3

## What is CVE-2018-3767?

CVE-2018-3767 is a critical denial of service vulnerability in https://github.com/memcachier memjs, published on 5 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`memjs` versions <= 1.1.0 allocates and stores buffers on typed input, resulting in DoS and uninitialized memory usage.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including memjs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `memjs` | npm | All versions to 1.2.0 | None |
| `memjs` | npm | All versions to 1.2.0 | None |

Products: Memcachier Memjs.

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

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

## Is CVE-2018-3767 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-3767 is a critical denial of service vulnerability in https://github.com/memcachier memjs, published on 5 Jul 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-3767 in the wild and no public exploit code.

Affected packages and fixed versions:
- memjs (npm): affected all versions up to 1.2.0; no fix listed
- memjs (npm): affected all versions up to 1.2.0; no fix listed

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

## Sources

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

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