Microsoft Edge: Bypass of fix for CVE-2023-36880
LowPublished Apr 4, 2024
### Summary A bypass in the fix for CVE-2023-36880 enables host process to change addresses between check and use in enclave as the arg pointer for the seal/unseal functions is dereferenced and its addresses are validated, then dereferenced again to get regions to read / write. ### Severity Low - This vulnerability enabled the host process to change addresses between check and use in enclave. ### Proof of Concept ``` SealSettings(args) { // <<---- args is on the enclave stack but the struct it points to is in the host process region if (!in_host_process(args->data_to_seal, args->sz_data_to_seal)) { // <<--- checked here return ERROR; } // << --- host process threads can write the region here size_t local_size = args->sz_data_to_seal + 4; void* local_buffer = malloc(local_size); // \/ ---- BUG - thread in host process may change args->data_to_seal before it is used in memcpy below. memcpy(local_buffer,args->data_to_seal, local_size); EnclaveSealData(local_buffer, local_size, args->protectedBlob, args->sz_protected_blob, &needed); return needed; } ``` ### Timeline **Date reported**: 12/14/2023 **Date fixed**: 2/28/2024 **Date disclosed**: 4/4/2024
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Edge Product | < https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21423 | https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-21423 |
Details and references
### Summary A bypass in the fix for CVE-2023-36880 enables host process to change addresses between check and use in enclave as the arg pointer for the seal/unseal functions is dereferenced and its addresses are validated, then dereferenced again to get regions to read / write. ### Severity Low - This vulnerability enabled the host process to change addresses between check and use in enclave. ### Proof of Concept ``` SealSettings(args) { // <<---- args is on the enclave stack but the struct it points to is in the host process region if (!in_host_process(args->data_to_seal, args->sz_data_to_seal)) { // <<--- checked here return ERROR; } // << --- host process threads can write the region here size_t local_size = args->sz_data_to_seal + 4; void* local_buffer = malloc(local_size); // \/ ---- BUG - thread in host process may change args->data_to_seal before it is used in memcpy below. memcpy(local_buffer,args->data_to_seal, local_size); EnclaveSealData(local_buffer, local_size, args->protectedBlob, args->sz_protected_blob, &needed); return needed; } ``` ### Timeline **Date reported**: 12/14/2023 **Date fixed**: 2/28/2024 **Date disclosed**: 4/4/2024
- Severity from
- GitHub (reviewed advisory)
More Google advisories
All Google| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| May 92024 | PostgreSQL: Anonymizer SQL Injection and Trusted Schema Bypasses | High | v1.3 |
| May 12024 | Python: Heap buffer overflow in a Pillow (PIL fork) interface to the littleCMS ICC Color Management System | Medium6.7 | 10.3.0 |
| Apr 52024 | UTM: Remote Code Execution Via Unsafe VM Handling | Medium | No fix yet |
| Apr 52024 | UTM: Unsafe URL Handling | Low | 4.5.1 |
| Mar 262024 | Python: Code Execution Vulnerability | Low | See the advisory |
| Mar 192024 | PostgreSQL: Concurrent Refresh Privilege Escalation | Medium | 12.18 |