CVE-2022-39313 json
Parse Server crashes when receiving file download request with invalid byte range
published 4y ago modified 2mo ago also BIT-parse-2022-39313 , EUVD-2022-7100 , GHSA-h423-w6qv-2wj3
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Versions prior to 4.10.17, and prior to 5.2.8 on the 5.x branch, crash when a file download request is received with an invalid byte range, resulting in a Denial of Service. This issue has been patched in versions 4.10.17, and 5.2.8. There are no known workarounds.
Patch / fix
- npm parse-server 4.10.17, 5.2.8
- bitnami parse 4.10.17, 5.2.8
- parseplatform parse-server 4.10.17, 5.2.8
Is CVE-2022-39313 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | parse-server | <4.10.17 >=5.0.0, <5.2.8 |
4.10.17 5.2.8 |
| bitnami | parse | <4.10.17 >=5.0.0, <5.2.8 |
4.10.17 5.2.8 |
Affected products
- parse-community parse-server
Classification
References
-
github.com
/parse-community/parse-server/commit/066f29673ab4030b6b5b90c0c0326f7d3fe7612a
web
-
github.com
/parse-community/parse-server/commit/3d7a61ecd5231638f01ff1a965b6313043c594a7
web
-
github.com
/parse-community/parse-server/security/advisories/GHSA-h423-w6qv-2wj3
web, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-39313
advisory, web
-
github.com
/parse-community/parse-server
package
-
github.com
/parse-community/parse-server/releases/tag/4.10.17
web
Sources
- CVE List CVE-2022-39313
- GitHub Advisory GHSA-h423-w6qv-2wj3
- NVD CVE-2022-39313
- OSV BIT-parse-2022-39313
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.