Bug 1128749

Summary: CVE-2014-3158 ppp: potential security vulnerability [fedora-all]
Product: [Fedora] Fedora Reporter: Vasyl Kaigorodov <vkaigoro>
Component: pppAssignee: Michal Sekletar <msekleta>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 20CC: jsynacek, msekleta, thozza
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ppp-2.4.5-33.fc19 Doc Type: Release Note
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-23 01:57:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1128748    

Description Vasyl Kaigorodov 2014-08-11 13:12: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 Vasyl Kaigorodov 2014-08-11 13:12:23 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=1128748,1128749

# Description of your update
notes=Security fix for CVE-2014-3158

# 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=1128748,1128749

Comment 2 Fedora Update System 2014-08-12 07:37:01 UTC
ppp-2.4.5-34.fc20 has been submitted as an update for Fedora 20.
https://admin.fedoraproject.org/updates/ppp-2.4.5-34.fc20

Comment 3 Fedora Update System 2014-08-12 07:38:38 UTC
ppp-2.4.5-33.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ppp-2.4.5-33.fc19

Comment 4 Fedora Update System 2014-08-15 02:53:21 UTC
Package ppp-2.4.5-33.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ppp-2.4.5-33.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-9401/ppp-2.4.5-33.fc19
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2014-08-23 01:57:47 UTC
ppp-2.4.5-34.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2014-08-30 03:52:57 UTC
ppp-2.4.5-33.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.