Bug 2135413 (CVE-2022-42915) - CVE-2022-42915 curl: HTTP proxy double-free
Summary: CVE-2022-42915 curl: HTTP proxy double-free
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-42915
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2135690 2135691 2138110 2138111
Blocks: 2135407
TreeView+ depends on / blocked
 
Reported: 2022-10-17 15:14 UTC by Marian Rehak
Modified: 2022-12-10 19:33 UTC (History)
15 users (show)

Fixed In Version: curl 7.86.0
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in curl. The issue occurs if curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL. It sets up the connection to the remote server by issuing a `CONNECT` request to the proxy and then tunnels the rest of the protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 response code to the client. Due to flaws in the error/cleanup handling, this could trigger a double-free issue in curl if using one of the following schemes in the URL for the transfer: `dict,` `gopher,` `gophers,` `ldap`, `ldaps`, `rtmp`, `rtmps`, `telnet.`
Clone Of:
Environment:
Last Closed: 2022-12-10 19:33:04 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:8840 0 None None None 2022-12-08 13:07:25 UTC
Red Hat Product Errata RHSA-2022:8841 0 None None None 2022-12-08 13:22:32 UTC

Description Marian Rehak 2022-10-17 15:14:14 UTC 
If curl is told to use an HTTP proxy for a transfer with a non-HTTP(S) URL, it sets up the connection to the remote server by issuing a `CONNECT` request to the proxy, and then *tunnels* the rest of protocol through. An HTTP proxy might refuse this request (HTTP proxies often only allow outgoing connections to specific port numbers, like 443 for HTTPS) and instead return a non-200 respons code to the client. Due to flaws in the error/cleanup handling, this could trigger a double-free in curl if one of the following schemes were used in the URL for the transfer: `dict`, `gopher`, `gophers`, `ldap`, `ldaps`, `rtmp`, `rtmps`, `telnet`

Reference:

https://curl.se/docs/CVE-2022-42915.html
Comment 4 Sandipan Roy 2022-10-27 09:26:23 UTC 
Created curl tracking bugs for this issue:

Affects: fedora-all [bug 2138111]


Created mingw-curl tracking bugs for this issue:

Affects: fedora-all [bug 2138110]
Comment 6 errata-xmlrpc 2022-12-08 13:07:23 UTC 
This issue has been addressed in the following products:

  JBoss Core Services on RHEL 7
  JBoss Core Services for RHEL 8

Via RHSA-2022:8840 https://access.redhat.com/errata/RHSA-2022:8840
Comment 7 errata-xmlrpc 2022-12-08 13:22:30 UTC 
This issue has been addressed in the following products:

  Red Hat JBoss Core Services

Via RHSA-2022:8841 https://access.redhat.com/errata/RHSA-2022:8841
Comment 8 Product Security DevOps Team 2022-12-10 19:33:02 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-42915
Note You need to log in before you can comment on or make changes to this bug.