Buffer under-read in workerd
Medium6.5CVE-2023-2512 · Published May 12, 2023
### Impact Prior to version v1.20230419.0, the FormData API implementation was subject to an integer overflow. If a FormData instance contained more than 2^31 elements, the `forEach()` method could end up reading from the wrong location in memory while iterating over elements. This would most likely lead to a segmentation fault, but could theoretically allow arbitrary undefined behavior. In order for the bug to be exploitable, the process would need to be able to allocate 160GB of RAM. Due to this, the bug was never exploitable on the Cloudflare Workers platform, but could theoretically be exploitable on deployments of workerd running on machines with a huge amount of memory. Moreover, in order to be remotely exploited, an attacker would have to upload a single form-encoded HTTP request of at least tens of gigabytes in size. The application code would then have to use `request.formData()` to parse the request and `formData.forEach()` to iterate over this data. Due to these limitations, the exploitation likelihood was considered Low. ### Patches A fix that addresses this vulnerability has been released in version v1.20230419.0 and users are encouraged to update to the latest versi...
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| workerd npm | < v1.20230419.0 | v1.20230419.0 |
Details and references
### Impact Prior to version v1.20230419.0, the FormData API implementation was subject to an integer overflow. If a FormData instance contained more than 2^31 elements, the `forEach()` method could end up reading from the wrong location in memory while iterating over elements. This would most likely lead to a segmentation fault, but could theoretically allow arbitrary undefined behavior. In order for the bug to be exploitable, the process would need to be able to allocate 160GB of RAM. Due to this, the bug was never exploitable on the Cloudflare Workers platform, but could theoretically be exploitable on deployments of workerd running on machines with a huge amount of memory. Moreover, in order to be remotely exploited, an attacker would have to upload a single form-encoded HTTP request of at least tens of gigabytes in size. The application code would then have to use `request.formData()` to parse the request and `formData.forEach()` to iterate over this data. Due to these limitations, the exploitation likelihood was considered Low. ### Patches A fix that addresses this vulnerability has been released in version v1.20230419.0 and users are encouraged to update to the latest version available. ### References Release - https://github.com/cloudflare/workerd/releases/tag/v1.20230419.0
- CVSS 3.1
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-127
More Cloudflare advisories
All Cloudflare| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Dec 122023 | Unbounded queuing of path validation messages in cloudflare-quiche | Medium5.3 | 0.19.1 |
| Dec 52023 | Resource exhaustion via memory leak in tokio-boring | Medium5.3 | 4.1.0 |
| Nov 212023 | WebSocket message can cause crash | Medium | v1.20231121.0 |
| Aug 32023 | Directory traversal vulnerability in Cloudflare Wrangler | Medium5.7 | 3.1.1+1 more |
| May 102023 | Improper random reading in CIRCL | Medium5.3 | 1.3.3 |
| Mar 212023 | Local Privilege Escalation Vulnerability in cloudflared's Installer | High7.5 | 2023.3.1 |