9.9.0
13 years ago
25 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 Regular Expression Denial of Service (ReDoS) via the How to fix Regular Expression Denial of Service (ReDoS)? Upgrade | <8.6.77>=9.0.0 <9.9.1-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 Race Condition due to a race condition in the How to fix Race Condition? Upgrade | <8.6.76>=9.0.0-alpha.1 <9.9.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 Insertion of Sensitive Information Into Sent Data via the How to fix Insertion of Sensitive Information Into Sent Data? Upgrade | >=7.0.0-alpha.1 <8.6.75>=9.0.0-alpha.1 <9.8.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 Timing Attack via the login endpoint. An attacker can determine whether a username or email exists in the database by measuring response times for login attempts. This is possible because the server responds faster when a user does not exist and slower when a user exists but the password is incorrect, due to the presence or absence of a bcrypt comparison. How to fix Timing Attack? Upgrade | <8.6.74>=9.0.0-alpha.1 <9.8.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 Interpretation Conflict via the file upload process. An attacker can cause files to be served with an unintended How to fix Interpretation Conflict? Upgrade | <8.6.73>=9.0.0-alpha.1 <9.7.1-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 Improper Authorization via the How to fix Improper Authorization? Upgrade | <8.6.71>=9.0.0 <9.7.1-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 Comparison via the How to fix Incorrect Comparison? Upgrade | <8.6.69>=9.0.0 <9.7.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 Access of Resource Using Incompatible Type ('Type Confusion') via the LiveQuery subscription process when an authenticated user with How to fix Access of Resource Using Incompatible Type ('Type Confusion')? Upgrade | <8.6.70>=9.0.0 <9.7.0-alpha.16 |
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 Inefficient Algorithmic Complexity in the GraphQL query complexity validation process. An attacker can cause the Node.js event loop to become blocked for several seconds by sending a specially crafted query with binary fan-out fragment spreads, resulting in denial of service to all concurrent users. This is only exploitable if the How to fix Inefficient Algorithmic Complexity? Upgrade | <8.6.68>=9.0.0 <9.7.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 Incorrect Authorization via the How to fix Incorrect Authorization? Upgrade | <8.6.67>=9.0.0 <9.7.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 Race Condition in the handling of concurrent LiveQuery subscribers due to shared mutable state. An attacker can access protected fields or authentication data belonging to other subscribers by subscribing multiple clients to the same class, leading to unintended data exposure. How to fix Race Condition? Upgrade | <8.6.65>=9.0.0-alpha.1 <9.7.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 Origin Validation Error via the GraphQL API endpoint ignoring the configured CORS How to fix Origin Validation Error? Upgrade | >=3.5.0 <8.6.66>=9.0.0-alpha.1 <9.7.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 Time-of-check Time-of-use (TOCTOU) Race Condition through the How to fix Time-of-check Time-of-use (TOCTOU) Race Condition? Upgrade | <8.6.64>=9.0.0 <9.7.0-alpha.8 |