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.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 18.04 | noarch | curl | < 7.58.0-2ubuntu3.24+esm1) Available with Ubuntu Pro or Ubuntu Pro (Infra-only | UNKNOWN |
ubuntu | 20.04 | noarch | curl | < 7.68.0-1ubuntu2.19 | UNKNOWN |
ubuntu | 22.04 | noarch | curl | < 7.81.0-1ubuntu1.11 | UNKNOWN |
ubuntu | 22.10 | noarch | curl | < 7.85.0-1ubuntu0.6 | UNKNOWN |
ubuntu | 23.04 | noarch | curl | < 7.88.1-8ubuntu2.1 | UNKNOWN |
ubuntu | 23.10 | noarch | curl | < 7.88.1-10ubuntu1 | UNKNOWN |
ubuntu | 24.04 | noarch | curl | < 7.88.1-10ubuntu1 | UNKNOWN |
ubuntu | 14.04 | noarch | curl | < 7.35.0-1ubuntu2.20+esm16) Available with Ubuntu Pro or Ubuntu Pro (Infra-only | UNKNOWN |
ubuntu | 16.04 | noarch | curl | < 7.47.0-1ubuntu2.19+esm9) Available with Ubuntu Pro or Ubuntu Pro (Infra-only | UNKNOWN |