#17233 closed enhancement (fixed)
curl-7.86.0
| Reported by: | Bruce Dubbs | Owned by: | Bruce Dubbs |
|---|---|---|---|
| Priority: | elevated | Milestone: | 11.3 |
| Component: | BOOK | Version: | git |
| Severity: | normal | Keywords: | |
| Cc: |
Description ¶
New minor version.
Change History (6)
comment:1 by , 2 years ago
| Priority: | normal → elevated |
|---|
comment:2 by , 2 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 2 years ago
comment:4 by , 2 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Fixed at commits
80cd2ac953 Update to PerlIO-utf8_strict-0.010 (Perl module). 32d7d10de3 Update to curl-7.86.0. 5bb1f9d35b Update to wireshark-4.0.1.
comment:5 by , 2 years ago
cURL Security Advisories:
CVE-2022-32221
CVE-2022-32221: POST following PUT confusion
============================================
Project curl Security Advisory, October 26 2022 -
[Permalink](https://curl.se/docs/CVE-2022-32221.html)
VULNERABILITY
-------------
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 was
used 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 subsequent
`POST` request.
The problem exists in the logic for a reused handle when it is changed from a
PUT to a POST.
We are not aware of any exploit of this flaw.
INFO
----
The code actually sending wrong data or doing a use-after-free is not present
in libcurl code but are only presumed scenarios that might become the outcome
of libcurl surprisingly calling the read callback in a situation where it is
not expected to.
This flaw cannot be triggered with the command line tool.
This issue was [reported and managed
publicly](https://github.com/curl/curl/issues/9507) before the security impact
was properly understood.
The Common Vulnerabilities and Exposures (CVE) project has assigned the name
CVE-2022-32221 to this issue.
CWE-440: Expected Behavior Violation
Severity: medium
AFFECTED VERSIONS
-----------------
- Affected versions: libcurl 7.7 to and including 7.85.0
- Not affected versions: libcurl < 7.7 and >= 7.86.0
libcurl is used by many applications, but not always advertised as such!
THE SOLUTION
------------
[The fix for
CVE-2022-32221](https://github.com/curl/curl/commit/a64e3e59938abd7d6) was
committed to the curl git repository and made public before the security
impact of this issue become clear to us. The securty impact was not
highlighted in the commit message nor surrounding messsaging.
RECOMMENDATIONS
--------------
A - Upgrade curl to version 7.86.0
B - Apply the patch to your local version
C - Do not do mix using the read callback and postfields string on a reused
easy handle
TIMELINE
--------
This issue was reported to the curl project on September 19, 2022. We
contacted distros@openwall on October 18, 2022.
libcurl 7.86.0 was released on October 26 2022, coordinated with the
publication of this advisory.
CVE-2022-35260
CVE-2022-35260: .netrc parser out-of-bounds access ================================================== Project curl Security Advisory, October 26 2022 - [Permalink](https://curl.se/docs/CVE-2022-35260.html) VULNERABILITY ------------- curl can be told to parse a `.netrc` file for credentials. If that file ends in a line with consecutive non-white space letters and no newline, curl could read past the end of the stack-based buffer, and if the read works, write a zero byte possibly beyond its boundary. This will in most cases cause a segfault or similar, but circumstances might also cause different outcomes. If a malicious user can provide a custom netrc file to an application or otherwise affect its contents, this flaw could be used as denial-of-service. We are not aware of any exploit of this flaw. INFO ---- The flaw was introduced in curl with [this commit](https://github.com/curl/curl/commit/eeaae10c0fb27aa06), first shipped in curl 7.84.0. The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2022-35260 to this issue. CWE-121: Stack-based Buffer Overflow Severity: low AFFECTED VERSIONS ----------------- - Affected versions: curl 7.84.0 to and including 7.85.0 - Not affected versions: curl < 7.84.0 and >= 7.86.0 libcurl is used by many applications, but not always advertised as such! THE SOLUTION ------------ [The fix for CVE-2022-35260](https://github.com/curl/curl/commit/c97ec984fb2bc919a3aa86) RECOMMENDATIONS --------------- A - Upgrade curl to version 7.86.0 B - Apply the patch to your local version C - Do not use `.netrc` files TIMELINE -------- This issue was reported to the curl project on October 3, 2022. We contacted distros@openwall on October 18, 2022. libcurl 7.86.0 was released on October 26 2022, coordinated with the publication of this advisory.
CVE-2022-42916
CVE-2022-42916: HSTS bypass via IDN =================================== Project curl Security Advisory, October 26 2022 - [Permalink](https://curl.se/docs/CVE-2022-42916.html) VULNERABILITY ------------- curl's HSTS check could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Like this: `http://curl。se。` We are not aware of any exploit of this flaw. INFO ---- This flaw was introduced in [commit 7385610d0c7](https://github.com/curl/curl/commit/7385610d0c7), which was shipped enabled by default from [commit d71ff2b9db566b3f](https://github.com/curl/curl/commit/d71ff2b9db566b3f) in curl 7.77.0. This issue is similar to the previous [CVE-2022-30115](https://curl.se/docs/CVE-2022-30115.html). The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2022-42916 to this issue. CWE-319: Cleartext Transmission of Sensitive Information Severity: Medium AFFECTED VERSIONS ----------------- - Affected versions: curl 7.77.0 to and including 7.85.0 - Not affected versions: curl < 7.77.0 and curl >= 7.86.0 libcurl is used by many applications, but not always advertised as such! THE SOLUTION ------------ A [fix for CVE-2022-42916](https://github.com/curl/curl/commit/53bcf55b4538067e6) RECOMMENDATIONS -------------- A - Upgrade curl to version 7.86.0 B - Apply the patch to your local version C - Stick to always using `HTTPS://` in URLs TIMELINE -------- This issue was reported to the curl project on October 11, 2022. We contacted distros@openwall on October 18, 2022. libcurl 7.86.0 was released on October 26 2022, coordinated with the publication of this advisory.
Note:
See TracTickets
for help on using tickets.
Version 7.86.0 (26 Oct 2022
This release includes the following changes:
This release includes the f-llowing bugfixes:
grep -Einstead ofegrep[30]Planned upc-ming removals include: