GHSA-hxcm-v35h-mg2x Prototype Pollution in querystringify
Not scored
Published
Check this codebase for GHSA-hxcm-v35h-mg2x and fix it if it is affected.
What it is: GHSA-hxcm-v35h-mg2x is a vulnerability in querystringify, published on 7 Jun 2019. 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-hxcm-v35h-mg2x in the wild and no public exploit code.
Affected packages and fixed versions:
- querystringify (npm): affected all versions; fixed in 2.0.0
- querystringify (npm): affected all versions; fixed in 2.0.0
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-hxcm-v35h-mg2x/ (Markdown: https://insights.sbomify.com/GHSA-hxcm-v35h-mg2x/index.md)
Attackers can pollute prototype properties via malicious query strings, potentially leading to code execution or security bypasses in applications using the library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-hxcm-v35h-mg2x?
GHSA-hxcm-v35h-mg2x is a vulnerability in querystringify, published on 7 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
A vulnerability was found in querystringify before 2.0.0. It's possible to override built-in properties of the resulting query string object if a malicious string is inserted in the query string.
Which versions are affected by GHSA-hxcm-v35h-mg2x?
2 open source packages ship an affected version, including querystringify.
| Package | Affected | Fixed in |
|---|---|---|
querystringify npm | All versions | 2.0.0 |
querystringify npm | All versions | 2.0.0 |
How do I fix GHSA-hxcm-v35h-mg2x?
Upgrade querystringify to 2.0.0 or later.
Is GHSA-hxcm-v35h-mg2x being exploited?
There is no known exploitation of GHSA-hxcm-v35h-mg2x in the wild and no public exploit code.