How to fix: Potential Prototype Pollution Sinks Detected
Vulnerable library functions that could allow modification of Object.prototype.
Why it matters
Prototype pollution can lead to XSS, privilege escalation, or denial of service.
Vulnerable functions like Lodash merge/set or jQuery.extend with deep merging can be exploited via __proto__ keys.
How to fix it
- 1Update vulnerable libraries: Lodash to 4.17.12+, jQuery to 3.4.0+.
- 2Use Object.create(null) for dictionary objects.
- 3Sanitize user input to reject __proto__ and constructor keys.
- 4Use Map instead of plain objects for user-controlled data.
Code examples
Safe merge
function safeMerge(target, source) {
for (const key of Object.keys(source)) {
if (key === '__proto__' || key === 'constructor' || key === 'prototype') continue;
target[key] = source[key];
}
}References
Detected automatically by VulnRadar. The check id is prototype-pollution, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
- MediuminnerHTML DOM XSS Sink
Questions
- How severe is Potential Prototype Pollution Sinks Detected?
- VulnRadar rates this medium severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id prototype-pollution, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Potential Prototype Pollution Sinks Detected map to?
- It maps to CWE-1321.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.