# GHSA-mh5c-679w-hh4r: Denial of Service in mongodb

> An attacker can crash the application by sending an invalid collection name to a non-existent database, causing a denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-mh5c-679w-hh4r?

GHSA-mh5c-679w-hh4r is a denial of service vulnerability in mongodb, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `mongodb` prior to 3.1.13 are vulnerable to Denial of Service. The package fails to properly catch an exception when a collection name is invalid and the DB does not exist, crashing the application.

## Recommendation

Upgrade to version 3.1.13 or later.

## Which versions are affected by GHSA-mh5c-679w-hh4r?

2 open source packages ship an affected version, including mongodb.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | npm | All versions | 3.1.13 |
| `mongodb` | npm | All versions | 3.1.13 |

## How do I fix GHSA-mh5c-679w-hh4r?

Upgrade mongodb to 3.1.13 or later.

## Is GHSA-mh5c-679w-hh4r being exploited?

There is no known exploitation of GHSA-mh5c-679w-hh4r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mh5c-679w-hh4r and fix it if it is affected.

What it is: GHSA-mh5c-679w-hh4r is a denial of service vulnerability in mongodb, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-mh5c-679w-hh4r in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (npm): affected all versions; fixed in 3.1.13
- mongodb (npm): affected all versions; fixed in 3.1.13

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/GHSA-mh5c-679w-hh4r/ (Markdown: https://insights.sbomify.com/GHSA-mh5c-679w-hh4r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mh5c-679w-hh4r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mh5c-679w-hh4r/
Summaries are generated and may contain mistakes; the official description above is the record.