Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

curl crashes with segm
Version-Release number of selected component (if applicable):

curl-7.29.0-48.el7

How reproducible:

Always

Steps to Reproduce:
1. curl -s --limit-rate 4m http://example.com/somebigfile
2.
3.

Actual results:

*** Error in `curl': free(): invalid pointer: 0x0000000001ea8270 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x81489)[0x7fe0ef8da489]
curl[0x4085dc]
curl[0x40238e]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fe0ef87b3d5]
curl[0x402412]
======= Memory map: ========
00400000-00425000 r-xp 00000000 fd:01 202452587                          /usr/bin/curl
00624000-00625000 r--p 00024000 fd:01 202452587                          /usr/bin/curl
00625000-00626000 rw-p 00025000 fd:01 202452587                          /usr/bin/curl
01e9c000-01ee0000 rw-p 00000000 00:00 0                                  [heap]
7fe0e0000000-7fe0e0021000 rw-p 00000000 00:00 0
7fe0e0021000-7fe0e4000000 ---p 00000000 00:00 0

or just

Segmentation Fault


Expected results:

rate limited download.

Additional info:

Testing prior releases indicates it is the -47 to -48 patches that introduced the regression.

Thank you for analyzing the issue!  It seems to be caused by:

    0061-curl-7.29.0-CVE-2018-1000122.patch

The following upstream commit triggers it:

    https://github.com/curl/curl/commit/curl-7_54_0-55-gc2ddc12

... and the following upstream commit fixes it:

    https://github.com/curl/curl/commit/curl-7_54_0-70-ge3ed5cb

I need to review all the commits from upstream pull request #1449:

    https://github.com/curl/curl/pull/1449/commits

... as they seem to be tightly dependent on each other.

I have backported additional 11 upstream commits to make the code consistent again:

https://github.com/curl/curl/commit/curl-7_54_0-58-g87eb8d5b3
https://github.com/curl/curl/commit/curl-7_54_0-60-gb8191e975
https://github.com/curl/curl/commit/curl-7_54_0-61-gf2fadf490
https://github.com/curl/curl/commit/curl-7_54_0-62-g40a074f25
https://github.com/curl/curl/commit/curl-7_54_0-63-g0cab3a394
https://github.com/curl/curl/commit/curl-7_54_0-65-g89cf6f38d
https://github.com/curl/curl/commit/curl-7_54_0-66-gc79f4908d
https://github.com/curl/curl/commit/curl-7_54_0-67-ge40e9d7f0
https://github.com/curl/curl/commit/curl-7_54_0-68-g7ee52c25f
https://github.com/curl/curl/commit/curl-7_54_0-70-ge3ed5cb38
https://github.com/curl/curl/commit/curl-7_54_0-72-geab6732fd

*** Bug 1702828 has been marked as a duplicate of this bug. ***

*** Bug 1710180 has been marked as a duplicate of this bug. ***

*** Bug 1724292 has been marked as a duplicate of this bug. ***

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:2181