Bug 2270500 (CVE-2024-2004) - CVE-2024-2004 curl: Usage of disabled protocol
Summary: CVE-2024-2004 curl: Usage of disabled protocol
Keywords:
Status: NEW
Alias: CVE-2024-2004
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2271827 2270501 2271826
Blocks: 2270489
TreeView+ depends on / blocked
 
Reported: 2024-03-20 15:35 UTC by Patrick Del Bello
Modified: 2024-03-28 16:58 UTC (History)
46 users (show)

Fixed In Version: curl 8.7.0
Doc Type: ---
Doc Text:
A flaw was found in curl. When a protocol selection parameter disables all protocols without adding any, the default set of protocols remains in the allowed set due to a logic error, allowing usage of disabled protocols.
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description Patrick Del Bello 2024-03-20 15:35:52 UTC
When a protocol selection parameter option disables all protocols without adding any then the default set of protocols would remain in the allowed set due to an error in the logic for removing protocols. The below command would perform a request to curl.se with a plaintext protocol which has been explicitly disabled.

     curl --proto -all,-http http://curl.se

The flaw is only present if the set of selected protocols disables the entire set of available protocols, in itself a command with no practical use and therefore unlikely to be encountered in real situations. The curl security team has thus assessed this to be low severity bug.

This flaw is also accessible using the curl command line tool.

Reference:
https://curl.se/docs/CVE-2024-2004.html

Upstream patch:
https://github.com/curl/curl/commit/17d302e56221

Comment 3 Guilherme de Almeida Suckevicz 2024-03-27 13:18:00 UTC
Created curl tracking bugs for this issue:

Affects: fedora-all [bug 2271826]


Created mingw-curl tracking bugs for this issue:

Affects: fedora-all [bug 2271827]


Note You need to log in before you can comment on or make changes to this bug.