parse-server: Improper Removal of Sensitive Information Before Storage or Transfer
CVE-2022-31112 is a high-severity improper removal of sensitive information before storage or transfer vulnerability in parse-server from Parse-community, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected parse-server versions: < 4.10.13; >= 5.0.0, < 5.2.4. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.34% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of parse-server you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Parse-community | parse-server | < 4.10.13; >= 5.0.0, < 5.2.4 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.2 | High | CNA (github.com) |
| CVSS 3.1 | 8.2 | High | NVD |
| CVSS 2.0 | 6.4 | Medium | NVD |
Official description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions parse Server LiveQuery does not remove protected fields in classes, passing them to the client. The LiveQueryController now removes protected fields from the client response. Users are advised to upgrade. Users unable t upgrade should use `Parse.Cloud.afterLiveQueryEvent` to manually remove protected fields.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Removal of Sensitive Information Before Storage or Transfer
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
How developers prevent this class of flaw
- Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
- Use naming conventions and strong types to make it easier to spot when sensitive data is being used. When creating structures, objects, or other complex entities, separate the sensitive and non-sensitive data as much as possible.
More Improper Removal of Sensitive Information Before Storage or Transfer vulnerabilities (CWE-212)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxhThird Party Advisory
Patches and release notes
- github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1Third Party Advisory
- github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6Third Party Advisory
- github.com/parse-community/parse-server/issues/8073Issue Tracking, Release Notes, Third Party Advisory
- github.com/parse-community/parse-server/pull/8074Release Notes, Third Party Advisory
- github.com/parse-community/parse-server/releases/tag/5.2.4Release Notes, Third Party Advisory
Other vulnerabilities in parse-server
- 7.5 High severity
- 8.8 High severity
- 7.4 High severity
- 8.2 High severity
- 7.5 High severity
- 7.4 High severity
Recent Improper Removal of Sensitive Information Before Storage or Transfer vulnerabilities
- 7.7 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.5 High severity
Spotted an error? Tell us.