fix: Cloud Code trigger context vulnerable to prototype pollution

[mtrezza]

Issue

Cloud Code trigger context vulnerable to prototype pollution

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, in-code descriptions)

[parse-github-assistant]

🚀 Thanks for opening this pull request! We appreciate your effort in improving the project. Please let us know once your pull request is ready for review.

Tip

• Keep pull requests small. Large PRs will be rejected. Break complex features into smaller, incremental PRs.
• Use Test Driven Development. Write failing tests before implementing functionality. Ensure tests pass.
• Group code into logical blocks. Add a short comment before each block to explain its purpose.
• We offer conceptual guidance. Coding is up to you. PRs must be merge-ready for human review.
• Our review focuses on concept, not quality. PRs with code issues will be rejected. Use an AI agent.
• Human review time is precious. Avoid review ping-pong. Inspect and test your AI-generated code.

Note

Please respond to review comments from AI agents just like you would to comments from a human reviewer. Let the reviewer resolve their own comments, unless they have reviewed and accepted your commit, or agreed with your explanation for why the feedback was incorrect.

Caution

Pull requests must be written using an AI agent with human supervision. Pull requests written entirely by a human will likely be rejected, because of lower code quality, higher review effort and the higher risk of introducing bugs. Please note that AI review comments on this pull request alone do not satisfy this requirement.

[parseplatformorg]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 598956e0-6e25-45e1-a123-f6277a09eba8

📥 Commits

Reviewing files that changed from the base of the PR and between bfe5ede and 4f4d5a9.

📒 Files selected for processing (1)

• spec/vulnerabilities.spec.js

🚧 Files skipped from review as they are similar to previous changes (1)

• spec/vulnerabilities.spec.js

---

📝 Walkthrough

Walkthrough

This PR hardens Cloud Code trigger request context against prototype pollution (GHSA-445j-ww4h-339m) by creating context objects with null prototypes and adds tests exercising header/body injection vectors to verify the fix.

Changes

Cohort / File(s)	Summary
Trigger request construction src/triggers.js	Changed request context creation to use Object.assign(Object.create(null), context) (null-prototype) instead of Object.assign({}, context), preventing prototype pollution via incoming context.
Vulnerability tests spec/vulnerabilities.spec.js	Added a new test suite for GHSA-445j-ww4h-339m with cases sending X-Parse-Cloud-Context and _context payloads (__proto__, constructor.prototype) and assertions that object prototypes and req.context are not polluted and deletions behave correctly.

Sequence Diagram(s)

(omitted — changes do not introduce a multi-component sequential flow requiring visualization)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• feat: Add request context middleware for config and dependency injection in hooks #8480: Modifies getRequestObject in src/triggers.js around request/config propagation, touching similar code paths for trigger request construction.

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	No pull request description was provided by the author. The PR description field is empty, which means required sections from the template (Issue, Approach, Tasks) are missing.	Add a comprehensive description following the template, including: the issue/vulnerability being fixed, the approach/changes made, and completion of relevant tasks (tests added, security checks, documentation updates).
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the fix: addressing a prototype pollution vulnerability in Cloud Code trigger context. It directly reflects the main change in the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@spec/vulnerabilities.spec.js`:
- Around line 5467-5535: The tests currently swallow request errors and then
allow assertions to pass if the cloud trigger never ran
(contextInTrigger/contextAfterDelete undefined); change each test to assert the
HTTP request succeeded and that the trigger executed before checking properties:
remove the .catch(e=>e) pattern on the await request calls (or capture the
response and assert a successful status), and add explicit assertions like
expect(contextInTrigger).toBeDefined() (for tests using contextInTrigger) and
expect(contextAfterDelete).toBeDefined() (for the deletion test) immediately
after the request to ensure Parse.Cloud.beforeSave handlers ran before asserting
prototype pollution checks.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e6f08268-7fd0-48f3-812d-ea5ef5005718

📥 Commits

Reviewing files that changed from the base of the PR and between e573cfa and bfe5ede.

📒 Files selected for processing (2)

• spec/vulnerabilities.spec.js
• src/triggers.js

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.50%. Comparing base (f63fd1a) to head (4f4d5a9).
⚠️ Report is 5 commits behind head on alpha.

Additional details and impacted files

@@           Coverage Diff           @@
##            alpha   #10352   +/-   ##
=======================================
  Coverage   92.50%   92.50%           
=======================================
  Files         192      192           
  Lines       16552    16552           
  Branches      231      231           
=======================================
  Hits        15312    15312           
  Misses       1218     1218           
  Partials       22       22           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[mtrezza]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[parseplatformorg]

🎉 This change has been released in version 9.7.0-alpha.17

[parseplatformorg]

🎉 This change has been released in version 9.7.0