9.6.1
13 years ago
1 days ago
Known vulnerabilities in the parse-server package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Uncontrolled Recursion via the Note: This is only exploitable if the LiveQuery WebSocket endpoint is accessible to untrusted clients. How to fix Uncontrolled Recursion? Upgrade | <8.6.56>=9.0.0 <9.6.0-alpha.45 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Information Exposure via the How to fix Information Exposure? Upgrade | <8.6.54>=9.0.0 <9.6.0-alpha.43 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in the LiveQuery WebSocket interface due to improper enforcement of pointer permissions. An attacker can gain unauthorized access to sensitive data by subscribing to real-time updates for objects in classes protected by pointer permissions, even if the pointer fields do not reference the subscribing user. How to fix Incorrect Authorization? Upgrade | <8.6.53>=9.0.0 <9.6.0-alpha.42 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Uncontrolled Recursion via the pre-validation transform pipeline. An attacker can cause the server process to become permanently unresponsive by sending an unauthenticated HTTP request with a deeply nested query containing logical operators. How to fix Uncontrolled Recursion? Upgrade | <8.6.55>=9.0.0-alpha.1 <9.6.0-alpha.44 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Missing Authentication for Critical Function due to the improper validation of third-party auth provider's credentials. An attacker can gain unauthorized access to user accounts by providing only the user's provider ID, bypassing credential verification. This is only exploitable if the server option How to fix Missing Authentication for Critical Function? Upgrade | <8.6.52>=9.0.0-alpha.1 <9.6.0-alpha.41 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Information Exposure through the Pages and legacy PublicAPI routes that do not respect How to fix Information Exposure? Upgrade | <8.6.51>=9.0.0-alpha.1 <9.6.0-alpha.40 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Information Exposure via the How to fix Information Exposure? Upgrade | <8.6.50>=9.0.0 <9.6.0-alpha.35 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improperly Controlled Sequential Memory Allocation in the Cloud function endpoint. An attacker can cause the server process to crash by invoking a cloud function endpoint with a specially crafted function name that traverses the JavaScript prototype chain of a registered cloud function handler, resulting in a stack overflow. How to fix Improperly Controlled Sequential Memory Allocation? Upgrade | <8.6.47>=9.0.0-alpha.1 <9.6.0-alpha.24 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Weak Authentication in the user sign up. An attacker can create authenticated sessions without providing valid credentials by submitting an empty How to fix Weak Authentication? Upgrade | <8.6.49>=9.0.0-alpha.1 <9.6.0-alpha.29 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Time-of-check Time-of-use (TOCTOU) Race Condition in the password reset mechanism. An attacker can gain unauthorized access to a user's account by intercepting a password reset token and submitting concurrent requests, potentially causing the attacker's password to be set instead of the legitimate user's. How to fix Time-of-check Time-of-use (TOCTOU) Race Condition? Upgrade | <8.6.48>=9.0.0-alpha.1 <9.6.0-alpha.28 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Prototype Pollution in the deep copy mechanism. An attacker can inject unauthorized fields into class schemas and bypass security restrictions by exploiting prototype pollution in the deep copy process. How to fix Prototype Pollution? Upgrade | <8.6.44>=9.0.0-alpha.1 <9.6.0-alpha.20 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improper Validation of Syntactic Correctness of Input in the LiveQuery subscription when an invalid regular expression pattern is provided. An attacker can cause the server process to terminate, resulting in denial of service for all connected clients by submitting a subscription request containing a malformed regular expression. How to fix Improper Validation of Syntactic Correctness of Input? Upgrade | <8.6.43>=9.0.0-alpha.1 <9.6.0-alpha.19 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improperly Controlled Modification of Dynamically-Determined Object Attributes via the How to fix Improperly Controlled Modification of Dynamically-Determined Object Attributes? Upgrade | <8.6.42>=9.0.0-alpha.1 <9.6.0-alpha.17 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Uncontrolled Recursion while processing of deeply nested query condition operators. An attacker can cause the server process to crash and deny service to all connected clients by sending a single crafted request. How to fix Uncontrolled Recursion? Upgrade | <8.6.45>=9.0.0-alpha.1 <9.6.0-alpha.21 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the file upload process. An attacker can execute arbitrary scripts in the user's browser by uploading files with specially crafted WorkaroundThis vulnerability can be mitigated by configuring the How to fix Cross-site Scripting (XSS)? Upgrade | <8.6.41>=9.0.0-alpha.1 <9.6.0-alpha.15 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Missing Authentication for Critical Function in the How to fix Missing Authentication for Critical Function? Upgrade | <8.6.40>=9.0.0-alpha.1 <9.6.0-alpha.14 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in the How to fix Incorrect Authorization? Upgrade | <8.6.21>=9.0.0-alpha.1 <9.5.2-alpha.8 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in the Keycloak authentication adapter due to missing validation of the Note: This is only exploitable if the Keycloak realm contains multiple client applications and the Keycloak authentication adapter is used. How to fix Incorrect Authorization? Upgrade | <8.6.18>=9.0.0-alpha.1 <9.5.2-alpha.5 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Function Call With Incorrect Order of Arguments in the OAuth2 authentication adapter when both How to fix Function Call With Incorrect Order of Arguments? Upgrade | >=8.0.2 <8.6.39>=9.0.0-alpha.1 <9.6.0-alpha.13 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Data Query Logic in the How to fix Improper Neutralization of Special Elements in Data Query Logic? Upgrade | <8.6.38>=9.0.0-alpha.1 <9.6.0-alpha.12 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Race Condition in the OAuth2 auth adapter. An attacker can gain unauthorized access by exploiting a race condition that causes token validation to occur against the wrong provider's configuration during concurrent authentication requests. This is only exploitable if multiple OAuth2 providers are configured via the How to fix Race Condition? Upgrade | <8.6.37>=9.0.0-alpha.1 <9.6.0-alpha.11 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Information Exposure in the LiveQuery subscription process. An attacker can infer the values of protected fields by crafting a subscription with a WHERE clause that references protected fields, including using dot-notation or Note: This is only exploitable if both protectedFields are configured in Class-Level Permissions and LiveQuery is enabled. How to fix Information Exposure? Upgrade | <8.6.35>=9.0.0-alpha.1 <9.6.0-alpha.9 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to SQL Injection via the Note: This is only exploitable if the deployment is configured to use PostgreSQL as the database and the attacker possesses the master key. How to fix SQL Injection? Upgrade | <8.6.36>=9.0.0-alpha.1 <9.6.0-alpha.10 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Missing Authorization via direct access to internal relationship tables through the REST API or GraphQL API using only the application key. An attacker can gain unauthorized permissions and access to protected resources by creating, reading, updating, or deleting records in any internal relationship table, which may result in bypassing access controls and escalating privileges. How to fix Missing Authorization? Upgrade | <8.6.20>=9.0.0-alpha.1 <9.5.2-alpha.7 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Insufficiently Protected Credentials in the OAuth2 authentication process when the Note: This is only exploitable if the generic OAuth2 authentication adapter is enabled with How to fix Insufficiently Protected Credentials? Upgrade | <8.6.22>=9.0.0-alpha.1 <9.5.2-alpha.9 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling through unbounded query complexity in the REST and GraphQL APIs. An attacker can exhaust server resources, such as CPU, memory, and database connections, by sending specially crafted queries that lack enforced complexity limits. How to fix Allocation of Resources Without Limits or Throttling? Upgrade | <8.6.15>=9.0.0-alpha.1 <9.5.2-alpha.2 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to SQL Injection in the How to fix SQL Injection? Upgrade | <8.6.31>=9.0.0-alpha.1 <9.6.0-alpha.5 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in Note: This is only exploitable if LiveQuery is enabled for classes with class-level permissions. How to fix Incorrect Authorization? Upgrade | <8.6.16>=9.0.0-alpha.1 <9.5.2-alpha.3 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improper Control of Interaction Frequency in the Note: This is only exploitable if the deployment relies solely on the built-in rate limiting feature without additional protections such as a reverse proxy or web application firewall. How to fix Improper Control of Interaction Frequency? Upgrade | <8.6.23>=9.0.0-alpha.1 <9.5.2-alpha.10 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Operation on a Resource after Expiration or Release due to the recovery code. An attacker can repeatedly gain unauthorized access to user accounts by reusing the same recovery code without it being invalidated. How to fix Operation on a Resource after Expiration or Release? Upgrade | <8.6.33>=9.0.0-alpha.1 <9.6.0-alpha.7 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improper Neutralization of Special Elements in Data Query Logic via the Note This is only exploitable if email verification or password reset is enabled and, for full email verification token extraction, if How to fix Improper Neutralization of Special Elements in Data Query Logic? Upgrade | <8.6.14>=9.0.0-alpha.1 <9.5.2-alpha.1 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in the handling of How to fix Incorrect Authorization? Upgrade | <8.6.32>=9.0.0-alpha.1 <9.6.0-alpha.6 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Information Exposure in the How to fix Information Exposure? Upgrade | <8.6.34>=9.0.0-alpha.1 <9.6.0-alpha.8 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the file upload. An attacker can execute arbitrary scripts in the context of the application domain by uploading specially crafted files with certain extensions or content types that are not blocked by default. This can lead to theft of session tokens, redirection of users, or unauthorized actions performed on behalf of users when the uploaded file is accessed in a browser. How to fix Cross-site Scripting (XSS)? Upgrade | <8.6.30>=9.0.0-alpha.1 <9.6.0-alpha.4 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to LDAP Injection via unsanitized input in the Note: This is only exploitable if the LDAP authentication adapter is enabled with group-based access control. How to fix LDAP Injection? Upgrade | <8.6.26>=9.0.0-alpha.1 <9.5.2-alpha.13 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Incorrect Authorization in the query validation. An authenticated user can access sensitive field values by wrapping constraints on protected fields inside logical query operators, thereby bypassing intended access restrictions. How to fix Incorrect Authorization? Upgrade | <8.6.19>=9.0.0-alpha.1 <9.5.2-alpha.6 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Missing Authorization via the generic How to fix Missing Authorization? Upgrade | <8.6.25>=9.0.0-alpha.1 <9.5.2-alpha.12 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to SQL Injection in the PostgreSQL storage adapter when processing How to fix SQL Injection? Upgrade | <8.6.29>=9.0.0-alpha.1 <9.6.0-alpha.3 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to SQL Injection in the handling of dot-notation field names with the Note: This is only exploitable if the deployment is configured to use a PostgreSQL database. How to fix SQL Injection? Upgrade | <8.6.28>=9.0.0-alpha.1 <9.6.0-alpha.2 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the file upload process. An attacker can execute arbitrary JavaScript in the context of the application origin by uploading a crafted SVG file containing malicious scripts, which are then served inline without protective headers. This can lead to theft of session tokens from How to fix Cross-site Scripting (XSS)? Upgrade | <8.6.17>=9.0.0 <9.5.2-alpha.4 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Prototype Pollution via How to fix Prototype Pollution? Upgrade | >=9.0.0-alpha.1 <9.5.1-alpha.2<8.6.13 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Improper Check for Unusual or Exceptional Conditions via the How to fix Improper Check for Unusual or Exceptional Conditions? Upgrade | >=9.0.0-alpha.1 <9.5.1-alpha.1<8.6.12 |
parse-server is a version of the Parse backend that can be deployed to any infrastructure that can run Node.js. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the handling of Note: This only affects LiveQuery subscription matching; Normal REST and GraphQL queries are not affected because their regex is evaluated by the database engine. How to fix Regular Expression Denial of Service (ReDoS)? Upgrade | <8.6.11>=9.0.0 <9.5.0-alpha.14 |