{"answers":{"affected":"5 open source packages ship an affected version, including parse-server and parse. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31112 in the wild and no public exploit code.","fix":"Upgrade parse-server to a fixed version for your release line: 4.10.13 or 5.2.4.","what":"CVE-2022-31112 is a high-severity vulnerability in Parseplatform Parse-Server, published on 30 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-31112 and fix it if it is affected.\n\nWhat it is: CVE-2022-31112 is a high-severity vulnerability in Parseplatform Parse-Server, published on 30 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-31112 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parse-server (npm): affected all versions; fixed in 4.10.13\n- parse-server (npm): affected all versions; fixed in 4.10.13\n- parse-server (npm): affected from 5.0.0; fixed in 5.2.4\n- parse-server (npm): affected from 5.0.0; fixed in 5.2.4\n- parse (Bitnami): affected all versions; fixed in 4.10.13, 5.2.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-31112/ (Markdown: https://insights.sbomify.com/CVE-2022-31112/index.md)","id":"CVE-2022-31112","markdown":"https://insights.sbomify.com/CVE-2022-31112/index.md","name":"CVE-2022-31112","record":{"aliases":["BIT-parse-2022-31112","GHSA-crrq-vr9j-fxxh"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Parse Server backend","requires_auth":"none","summary":"Parse Server LiveQuery fails to remove protected fields, allowing attackers to read sensitive data from the client response.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"parse-server","vendor":"parseplatform"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-212","name":"Improper Removal of Sensitive Information Before Storage or Transfer"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":["Bitnami","npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Protected fields exposed via LiveQuery in parse-server","id":"CVE-2022-31112","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"parseplatform:parse-server","products":["parseplatform:parse-server"],"type":"information_disclosure","year":"2022"},"n_packages":5,"n_references":6,"next":{"headline":"Cross-Site Scripting in Canarytoken history","id":"CVE-2022-31113"},"packages":[{"ecosystem":"Bitnami","fixed":["4.10.13","5.2.4"],"introduced":["0","5.0.0"],"last_affected":[],"package":"parse","purl":"pkg:bitnami/parse","source":"BIT-parse-2022-31112"},{"ecosystem":"npm","fixed":["4.10.13"],"introduced":["0"],"last_affected":[],"package":"parse-server","purl":null,"source":"GHSA-crrq-vr9j-fxxh"},{"ecosystem":"npm","fixed":["4.10.13"],"introduced":["0"],"last_affected":[],"package":"parse-server","purl":"pkg:npm/parse-server","source":"GHSA-crrq-vr9j-fxxh"},{"ecosystem":"npm","fixed":["5.2.4"],"introduced":["5.0.0"],"last_affected":[],"package":"parse-server","purl":null,"source":"GHSA-crrq-vr9j-fxxh"},{"ecosystem":"npm","fixed":["5.2.4"],"introduced":["5.0.0"],"last_affected":[],"package":"parse-server","purl":"pkg:npm/parse-server","source":"GHSA-crrq-vr9j-fxxh"}],"prev":{"headline":"Discrepency in transfer value and actual value due to incorrect truncation in Frontier","id":"CVE-2022-31111"},"products":["parse-server"],"published":"2022-06-30","related":[{"cvss_score":10,"headline":"Parse Server role escalation and CLP bypass via direct `_Join` table write","id":"CVE-2026-30966","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":10,"headline":"Parse Server literalizeRegexPart SQL Injection","id":"CVE-2024-27298","kev_date_added":null,"published":"2024-03-01"},{"cvss_score":10,"headline":"Command Injection in Parse server","id":"CVE-2022-24760","kev_date_added":null,"published":"2022-03-11"},{"cvss_score":9.9,"headline":"Parse Server session token exfiltration via `redirectClassNameForKey` query parameter","id":"CVE-2026-30965","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":9.8,"headline":"Parse Server vulnerable to remote code execution via MongoDB BSON parser through prototype pollution","id":"CVE-2023-36475","kev_date_added":null,"published":"2023-06-28"},{"cvss_score":9.8,"headline":"Parse Server vulnerable to Remote Code Execution via prototype pollution in MongoDB BSON parser","id":"CVE-2022-39396","kev_date_added":null,"published":"2022-11-10"},{"cvss_score":9.3,"headline":"Parse Server: Account takeover via operator injection in authentication data identifier","id":"CVE-2026-32248","kev_date_added":null,"published":"2026-03-12"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["parse-community"]},"summary":"Parse Server LiveQuery fails to remove protected fields, allowing attackers to read sensitive data from the client response.","url":"https://insights.sbomify.com/CVE-2022-31112/"}