3.7

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2023-28322

CVE-2023-28322: An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers,...

An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2023-28322

CVE-2023-28322:

3.7

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability (CVE-2023-28322) occurs when a cURL handle is reused: first for a PUT request with a read callback (CURLOPT_READFUNCTION), and then for a POST request with CURLOPT_POSTFIELDS. Libcurl would erroneously use the old read callback for the POST request.

The primary fix is in Curl_vsetopt (in lib/url.c). When CURLOPT_POSTFIELDS is set, the code now checks if the handle was previously used for a PUT with a read callback (data->state.upload_from_put). If so, it explicitly clears the read callback function pointer (data->state.fread_func) and its associated input pointer (data->state.in). This prevents the stale callback from being used.

Curl_fillreadbuffer (in lib/sendf.c) is the function that actually invokes the fread_func. While not patched itself for this CVE, it's the component that would perform the erroneous action (calling the stale callback) if the state managed by Curl_vsetopt was incorrect. Therefore, it's a runtime indicator of where the faulty logic would manifest. The user-provided read callback function would also appear in stack traces, invoked by Curl_fillreadbuffer.

The analysis is based on the commit 091323241edd7339a37393f68777a4a1519e1859 from the curl/curl repository, which addresses CVE-2023-28322, as identified from PR #10949.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.