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 creating a Bodhi update request, please use the bodhi submission link noted 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 Bodhi notes field when available. Please note: this issue affects multiple supported versions of Fedora. Only one tracking bug has been filed; please ensure that it is only closed when all affected versions are fixed. [bug automatically created by: add-tracking-bugs]
Please use the following update submission link to create the Bodhi request 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. Please also ensure that the "Close bugs when update is stable" option remains checked. Bodhi update submission link: https://admin.fedoraproject.org/updates/new/?type_=security&bugs=881399,881411
This is similar to bug 873262. Fedora elinks is built against nss_compat_ossl, so this vulnerability does not apply. I propose to close this out.
But the problem exists, so how can you say it doesn't apply? I reproduced it, using steps from the parent bug.
Sorry, the above statement is incorrect. Fedora elinks suffers from this issue.
This seems to be the upstream fix: http://repo.or.cz/w/elinks.git/commitdiff/0c3f3e09
nss_compat_ossl does not seem to be ready for the upstream solutioin. A possible hotfix would be to bypass nss_compat_ossl and call SSL_SetURL() from NSS directly. The NSS default cert verification callback should then take care of the hostname validation. But first I need to make sure that the NSS default cert verification callback is actually used by ELinks.
(In reply to comment #6) > nss_compat_ossl does not seem to be ready for the upstream solutioin. A > possible hotfix would be to bypass nss_compat_ossl and call SSL_SetURL() > from NSS directly. The NSS default cert verification callback should then > take care of the hostname validation. But first I need to make sure that > the NSS default cert verification callback is actually used by ELinks. I have checked the sources of nss_compat_ossl and it explicitly ignores the hostname mismatch error: err = PORT_GetError(); switch (err) { case SEC_ERROR_CERT_VALID: case SSL_ERROR_BAD_CERT_DOMAIN: /* We don't set set the hostname so we can * safely ignore this. In OpenSSL the * caller is responsible. */ err = X509_V_OK; break; Consequently, calling SSL_SetURL() has no effect anyway.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Created attachment 799344 [details] proposed fix See bug #910815 for the related discussion about possible solutions.
fixed in elinks-0.12-0.37.pre6.fc21
Created attachment 800033 [details] proposed fix V2
elinks-0.12-0.36.pre6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/elinks-0.12-0.36.pre6.fc20
elinks-0.12-0.33.pre6.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/elinks-0.12-0.33.pre6.fc18
elinks-0.12-0.35.pre6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/elinks-0.12-0.35.pre6.fc19
Package elinks-0.12-0.36.pre6.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing elinks-0.12-0.36.pre6.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18323/elinks-0.12-0.36.pre6.fc20 then log in and leave karma (feedback).
elinks-0.12-0.36.pre6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
elinks-0.12-0.33.pre6.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
elinks-0.12-0.35.pre6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
Note this change caused #1099423.
Just to provide more context, this patch is causing https://gcc.gnu.org from working (when it works with firefox, wget, etc.). So there is something definitely wrong with this patch, as noted in bug #1099423. Instead of re-opening this bug, use the other to fix and I'll note in the top-level bug that this patch caused a problem.
As far as I know, there is nothing wrong with this patch. Bug #1099423 iss a problem in nss_compat_ossl, which broke due to NSS returning failures when SSLv2 is enabled.