|Summary:||CVE-2015-2694 krb5: issues in OTP and PKINIT kdcpreauth modules leading to requires_preauth bypass [fedora-21]|
|Product:||[Fedora] Fedora||Reporter:||Martin Prpič <mprpic>|
|Component:||krb5||Assignee:||Roland Mainz <rmainz>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||21||CC:||dpal, kerberos-dev-list, nalin, nathaniel, rharwood, rmainz|
|Target Milestone:||---||Keywords:||Security, SecurityTracking|
|Fixed In Version:||krb5-1.12.2-17.fc21||Doc Type:||Release Note|
|Doc Text:||Story Points:||---|
|Last Closed:||2015-05-11 19:02:46 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Martin Prpič 2015-04-28 14:47:33 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. fedora-21 tracking bug for krb5: see blocks bug list for full details of the security issue(s). This bug is never intended to be made public, please put any public notes in the blocked bugs. [bug automatically created by: add-tracking-bugs]
Comment 1 Martin Prpič 2015-04-28 14:47:37 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=1216133,1216134 # Description of your update notes=Security fix for CVE-2015-2694 # 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=1216133,1216134
Comment 2 Roland Mainz 2015-05-06 00:47:42 UTC
Accepting bug ...
Comment 3 Fedora Update System 2015-05-06 00:51:13 UTC
krb5-1.13.1-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/krb5-1.13.1-3.fc22
Comment 4 Fedora Update System 2015-05-06 00:55:22 UTC
krb5-1.12.2-17.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/krb5-1.12.2-17.fc21
Comment 5 Roland Mainz 2015-05-06 00:57:13 UTC
Fixed in the following Fedora builds... krb5-1.12.2-17.fc21 krb5-1.13.1-3.fc22 krb5-1.13.1-4.fc23 ... marking bug as MODIFIED.
Comment 6 Fedora Update System 2015-05-10 23:48:41 UTC
Package krb5-1.12.2-17.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing krb5-1.12.2-17.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7878/krb5-1.12.2-17.fc21 then log in and leave karma (feedback).
Comment 7 Fedora Update System 2015-05-11 19:02:46 UTC
krb5-1.13.1-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 8 Fedora Update System 2015-06-21 00:28:35 UTC
krb5-1.12.2-17.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.