Details
Affected Versions
Ecosystem: npmPackage: @apostrophecms/db-connectConfirmed affected range: >= 1.0.0, <= 1.0.2Latest release checked: 1.0.2 (npm registry)Fix status: not fixed
The unguarded unsetNestedField and the exclusion-branch applyProjection call are byte-identical across the published stable releases 1.0.0, 1.0.1, and 1.0.2, and the SQLite and PostgreSQL adapters invoke applyProjection per returned document in all of them. No published release fixes the issue. The prerelease line (1.0.0-alpha.1, 1.0.0-alpha.2, 1.0.2-alpha.0) ships the same code but is outside the supported stable channel. Reachability requires a consumer on a SQLite, PostgreSQL, or multipostgres adapter; the default mongodb adapter delegates the projection to the real MongoDB driver and is not affected. The apostrophe package, which drives reachability, declares @apostrophecms/db-connect@^1.0.1, resolving to the affected 1.0.2.
Suggested Fix
Enforce that untrusted field paths can never traverse into shared prototype objects. Both unsetNestedField and setNestedField in packages/db-connect/lib/shared.js should reject any path whose segments include __proto__, constructor, or prototype, mirroring the unsafePathSegments guard already used in the apostrophe package's apos.util.set/get; equivalently, the helpers can traverse own-properties only (for example using Object.prototype.hasOwnProperty checks captured before use, or Map-based access) so that resolution cannot reach prototype objects. Because applyProjection is the reachable gate, adding the guard at the helper level protects every adapter path at once. As an interim mitigation without a code change, deployments can run on the default mongodb adapter (which is not affected) or restrict authenticated API access so that only fully trusted roles can reach the piece-type REST endpoints.
Reported by zx (GitHub: @manus-pi).