Security Digest · Vulnerability record

CVE-2024-29027: Server crashes on invalid Cloud Function or Cloud Job name

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js.

CVSS 9.1 Critical EPSS 1.2% · p68

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 1.2%, percentile 68: FIRST’s model estimates a 1.2% chance of exploitation activity in the next 30 days, higher than 68% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes parse-server (npm) < 6.5.5, fixed in 6.5.5; parse-server (npm) >= 7.0.0-alpha.1, < 7.0.0-alpha.29, fixed in 7.0.0-alpha.29. Check your lockfile, including transitive dependencies.

What it is

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 6.5.5 and 7.0.0-alpha.29, calling an invalid Parse Server Cloud Function name or Cloud Job name crashes the server and may allow for code injection, internal store manipulation or remote code execution. The patch in versions 6.5.5 and 7.0.0-alpha.29 added string sanitation for Cloud Function name and Cloud Job name. As a workaround, sanitize the Cloud Function name and Cloud Job name before it reaches Parse Server.

From the GitHub advisory

Impact

Calling an invalid Parse Server Cloud Function name or Cloud Job name crashes server and may allow for code injection.

Patches

Added string sanitation for Cloud Function name and Cloud Job name.

Workarounds

Weakness type: CWE-74, CWE-20.

Product: parse-server (npm) · Assigned by: GitHub_M · Published: 2024-03-19

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
npmparse-server< 6.5.56.5.5
npmparse-server>= 7.0.0-alpha.1, < 7.0.0-alpha.297.0.0-alpha.29
VendorProductAffected versions (per CVE record)
parse-communityparse-server< 6.5.5, >= 7.0.0-alpha.1, < 7.0.0-alpha.29

Severity scores

Scored byCVSSScoreVector
GitHub_M3.19.1 CriticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
GitHub3.19.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: high (needs special conditions)
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: changed (can affect other components)

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable no, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 1.19% probability of exploitation activity in the next 30 days; percentile 68.

Timeline

  • — CVE record published by GitHub_M
  • — GitHub-reviewed advisory GHSA-6hh7-46r2-vf29 published (critical)
  • — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-6hh7-46r2-vf29 github.com
  2. CVE.org record CVE-2024-29027 cve.org
  3. NVD entry CVE-2024-29027 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com

Critical npm advisories · Today’s Security Digest