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]
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=1071466,1151515 # Description of your update notes=Security fix for CVE-2014-0104 # 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=1071466,1151515
Hello fdinitto, You plan to fix this soon?
(In reply to pjp from comment #2) > Hello fdinitto, > > You plan to fix this soon? I believe Marek fixed it months ago and the fix is already in Fedora. Marek can you confirm?
As is mentioned in CVE, this problem is only in RHEL6 where --ssl is transcribed to --ssl-insecure (no verification of SSL certificate) to not break existing installation. Starting from RHEL7 the default is --ssl => --ssl-secure, the very same approach is used in Fedora releases. So, by default SSL certificates are verified but user can disable that verification using --ssl-insecure