How severe is GHSA-mh5c-679w-hh4r?

No CVSS score has been assigned to GHSA-mh5c-679w-hh4r yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mh5c-679w-hh4r?

GHSA-mh5c-679w-hh4r affects the following packages: mongodb (npm). Ecosystems affected: npm.

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

Update mongodb to 3.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mh5c-679w-hh4r is resolved across your whole dependency graph.

How do I detect GHSA-mh5c-679w-hh4r in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mh5c-679w-hh4r if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-mh5c-679w-hh4r?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mh5c-679w-hh4r can be triaged on real exposure rather than presence alone.

Is GHSA-mh5c-679w-hh4r actively exploited in the wild?

No public exploit code has been indexed for GHSA-mh5c-679w-hh4r yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-mh5c-679w-hh4r published, and has it been updated?

GHSA-mh5c-679w-hh4r was published on September 3, 2020 and was last updated on August 31, 2020. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-mh5c-679w-hh4r — mongodb

GHSA-mh5c-679w-hh4r is a security vulnerability in mongodb. A fix is available for mongodb — see the affected versions and patch details below.

Denial of Service in mongodb

Published

Sep 3, 2020

Updated

Aug 31, 2020

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 31, 2020 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

15Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mongodbnpm

10.6Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mongodb`	all versions	3.1.13`npm install mongodb@3.1.13`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mongodb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mongodb to 3.1.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mh5c-679w-hh4r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mh5c-679w-hh4r can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mh5c-679w-hh4r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-mh5c-679w-hh4r in your dependencies?

O3 Security finds GHSA-mh5c-679w-hh4r across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works