Bug 1214181 - CVE-2015-3144 curl: host name out of boundary memory access [fedora-all]
Summary: CVE-2015-3144 curl: host name out of boundary memory access [fedora-all]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: curl
Version: 21
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2015-3144
TreeView+ depends on / blocked
 
Reported: 2015-04-22 07:56 UTC by Martin Prpič
Modified: 2015-05-02 18:11 UTC (History)
2 users (show)

Fixed In Version: curl-7.37.0-14.fc21
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-26 12:42:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Prpič 2015-04-22 07:56:20 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

[bug automatically created by: add-tracking-bugs]

Comment 1 Martin Prpič 2015-04-22 07:56:26 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1213335,1214181

# Description of your update
notes=Security fix for CVE-2015-3144

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi update submission link instead:

https://admin.fedoraproject.org/updates/new/?type_=security&bugs=1213335,1214181

Comment 2 Kamil Dudka 2015-04-22 14:31:30 UTC
fixed in curl-7.42.0-1.fc23

Comment 3 Fedora Update System 2015-04-22 14:38:16 UTC
curl-7.40.0-3.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/curl-7.40.0-3.fc22

Comment 4 Fedora Update System 2015-04-22 14:40:43 UTC
curl-7.37.0-14.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/curl-7.37.0-14.fc21

Comment 5 Fedora Update System 2015-04-23 16:03:46 UTC
Package curl-7.40.0-3.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing curl-7.40.0-3.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-6695/curl-7.40.0-3.fc22
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2015-04-26 12:42:27 UTC
curl-7.40.0-3.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2015-05-02 18:11:18 UTC
curl-7.37.0-14.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.


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