7.4.0
11 years ago
2 days ago
Known vulnerabilities in the parse-server package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for freeVulnerability | 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 Improper Authorization when the How to fix Improper Authorization? Upgrade | <6.5.9>=7.0.0 <7.3.0 |
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 when Parse Server is configured to use the How to fix SQL Injection? Upgrade | <6.5.7>=7.0.0 <7.1.0 |
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 Input Validation for Cloud Function names and Cloud Job names. Exploiting this vulnerability allows an attacker to cause a denial of service or execute arbitrary code by sending a specially crafted request. How to fix Improper Input Validation? Upgrade | <6.5.5>=7.0.0-alpha.1 <7.0.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 SQL Injection via a malicious PostgreSQL statement containing multiple quoted strings. This vulnerability is only present when the PostgreSQL engine is in use. How to fix SQL Injection? Upgrade | <6.5.0>=7.0.0-alpha.1 <7.0.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 Uncontrolled Resource Consumption ('Resource Exhaustion') via the file upload function. An attacker can cause the server to crash by uploading a file without an extension. How to fix Uncontrolled Resource Consumption ('Resource Exhaustion')? Upgrade | >=1.0.0 <5.5.6>=6.0.0 <6.3.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 Access Restriction Bypass via the How to fix Access Restriction Bypass? Upgrade | >=1.0.0 <5.5.5>=6.0.0 <6.2.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 Prototype Pollution in the MongoDB BSON parser, which allows attackers to execute code on the affected system. How to fix Prototype Pollution? Upgrade | <5.5.2>=6.0.0-alpha.1 <6.2.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 Arbitrary File Upload such that a malicious user could upload an HTML file to Parse Server via its public API. That HTML file would then be accessible at the internet domain at which Parse Server is hosted. The URL of the uploaded HTML could be shared for phishing attacks. The HTML page may seem legitimate because it is served under the internet domain where Parse Server is hosted, which may be the same as a company's official website domain. Note: An additional security issue arises when the Parse JavaScript SDK is used. The SDK stores sessions in the internet browser's local storage, which usually restricts data access depending on the internet domain. A malicious HTML file could contain a script that retrieves the user's session token from local storage and then share it with the attacker. How to fix Arbitrary File Upload? Upgrade | <5.5.0>=6.0.0 <6.2.0 |
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 Authentication Bypass due to insufficient checks in the mechanism used to determine the client's IP address. How to fix Authentication Bypass? Upgrade | <5.4.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 Prototype Pollution such that a compromised Parse Server Cloud Code Webhook target endpoint allows an attacker to use prototype pollution to bypass the Parse Server How to fix Prototype Pollution? Upgrade | <4.10.20>=5.0.0 <5.3.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 Prototype Pollution such that keywords that are specified in the Parse Server option How to fix Prototype Pollution? Upgrade | <4.10.19>=5.0.0 <5.3.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 Prototype Pollution due to insufficient validation checks which can allow an attacker to trigger remote code execution. How to fix Prototype Pollution? Upgrade | <4.10.18>=5.0.0 <5.3.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 Denial of Service (DoS) when receiving a file download request with an invalid byte range. How to fix Denial of Service (DoS)? Upgrade | <4.10.17>=5.0.0 <5.2.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 Authentication Bypass where the session object properties can be updated by a foreign user if the object ID is known. How to fix Authentication Bypass? Upgrade | <4.10.15>=5.0.0 <5.2.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 Improper Authentication when the server-side authentication adapter configuration Note:
This vulnerability affects environments with configurations that allow users to authenticate using the Parse Server authentication adapter for How to fix Improper Authentication? Upgrade | <4.10.16>=5.0.0 <5.2.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 Information Exposure via internal fields (keys used internally by Parse Server, prefixed by How to fix Information Exposure? Upgrade | <4.10.14>=5.0.0 <5.2.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 Information Exposure because the How to fix Information Exposure? Upgrade | <4.10.13>=5.0.0 <5.2.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 Denial of Service (DoS) due to certain types of invalid files requests are not handled properly. Note: If you are running multiple Parse Server instances in a cluster, the availability impact may be low. If you are running Parse Server as a single instance without redundancy, the availability impact may be high. How to fix Denial of Service (DoS)? Upgrade | <4.10.12>=5.0.0 <5.2.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 Authentication Bypass due to missing validation of certificates from Apple Game Center.
Thus, authentication could potentially be bypassed by making a fake certificate accessible via certain Apple domains and providing the URL to that certificate in an How to fix Authentication Bypass? Upgrade | <4.10.11>=5.0.0 <5.2.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 Authentication Bypass due to a weak validation of the How to fix Authentication Bypass? Upgrade | <4.10.10>=5.0.0 <5.2.1 |