GHSA-2cp6-34r9-54xx is a medium-severity (CVSS 6.5) CWE-1321 vulnerability in makerjs. O3 Security confirms whether GHSA-2cp6-34r9-54xx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Maker.js has Unsafe Property Copying in makerjs.extendObject
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
makerjsnpmDescription
Summary
The makerjs.extendObject function copies properties from source objects without proper validation, potentially exposing applications to security risks. The function lacks hasOwnProperty() checks and does not filter dangerous keys, allowing inherited properties and potentially malicious properties to be copied to target objects.
Details
The extendObject function iterates over source object properties using a for...in loop without:
- Checking
hasOwnProperty()to exclude inherited properties - Filtering dangerous keys (
__proto__,constructor,prototype) - Validating property sources
Affected Code
PoC
const makerjs = require('makerjs');
const source = { __proto__: { name: 'Ravi', isAdmin: true } };
const target = { name: 'user' };
const result = makerjs.extendObject(target, source);
console.log(result.name); // Ravi
console.log(result.isAdmin); // true
Impact
Security Implications
-
Unexpected Behavior: Properties may appear on target objects but not be own properties, breaking
hasOwnProperty()assumptions in security-sensitive code. -
Security Bypass Risk: Code relying on
hasOwnProperty()for validation could be bypassed. -
Future Risk: Lack of dangerous key filtering (
__proto__,constructor,prototype) exposes potential attack vectors.
Affected Use Cases
- Extending objects from user input or external APIs
- Merging options from untrusted sources
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | makerjs | all versions | 0.19.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for makerjs. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update makerjs to 0.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2cp6-34r9-54xx 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 pinpoints whether GHSA-2cp6-34r9-54xx is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2cp6-34r9-54xx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2cp6-34r9-54xx in your dependencies?
O3 detects GHSA-2cp6-34r9-54xx across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.