Prototype Pollution in get-setter
Priority LOW 38CWE-1321Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
All versions of `get-setter` are vulnerable to prototype pollution. The function `set` does not restrict the modification of an Object's prototype, which may allow an attacker to add or modify an existing property that will exist on all objects. ## Recommendation No fix is currently available. Consider using an alternative package until a fix is made available.
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | get-setter (npm) | 0.0.0 and later | — | No fix listed | GHSA-ch82-gqh6-9xj9 |
- get-setter (npm) Vendor— Affected 0.0.0 and later Fixed in — No fix listed GHSA-ch82-gqh6-9xj9
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-ch82-gqh6-9xj9
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences