Security readout for executives and security teams
Plain-English summary
Parse Server deployments using LiveQuery could send fields marked as protected to clients. This is mainly a confidentiality issue: sensitive application data meant to be hidden could be exposed without user interaction. The public sources advise upgrading or manually filtering LiveQuery events if upgrading is not possible.
Executive priority
Treat as high priority for Parse Server applications using LiveQuery, especially where protected fields contain personal, credential, or business-sensitive data. Remediation is version-driven and should be scheduled promptly, with emergency handling for internet-facing or multi-tenant deployments.
Technical view
CVE-2022-31112 is a CWE-200 issue in parse-community parse-server. Affected LiveQuery responses did not remove protected fields before sending class data to clients. Affected versions are <4.10.13 and >=5.0.0, <5.2.4. CVSS 3.1 is 8.2, driven by network reachability, no privileges, and high confidentiality impact.
Likely exposure
Exposure is likely where an application runs vulnerable parse-server versions and uses LiveQuery on classes containing protected fields. The source bundle does not indicate specific hosted services, default configurations, or downstream products beyond parse-server itself.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The weakness is remotely reachable in affected deployments using LiveQuery, but the provided sources do not prove public exploitation or provide incident evidence.
Researcher notes
The fix is described as LiveQueryController removing protected fields from client responses. Evidence is strongest for affected versions, impact, and workaround. Evidence is incomplete for real-world exploitation, exact data types exposed, and application-specific blast radius.
Mitigation direction
- Upgrade parse-server to a fixed version outside the affected ranges.
- Prioritize upgrade for deployments using LiveQuery with protected fields.
- If unable to upgrade, use Parse.Cloud.afterLiveQueryEvent to remove protected fields.
- Review vendor advisory and release notes before production rollout.
- Monitor for further parse-server guidance if running customized LiveQuery logic.
Validation and detection
- Inventory parse-server package versions in application manifests and deployed artifacts.
- Confirm whether LiveQuery is enabled in affected applications.
- Identify classes using protected fields and LiveQuery subscriptions.
- After remediation, confirm LiveQuery responses no longer include protected fields.
- Review logs cautiously; the sources do not define reliable exploit indicators.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31112 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N3.94.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxhCVE reference · x_refsource_CONFIRM
- https://github.com/parse-community/parse-server/issues/8073CVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-server/pull/8074CVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1CVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6CVE reference · x_refsource_MISC
- https://github.com/parse-community/parse-server/releases/tag/5.2.4CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.