Latest upstream release: 0.5.5
Current version/release in Fedora Rawhide: 0.5.4-4.fc21
Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy
More information about the service that created this bug can be found at:
libinfinity-0.5.5-1.fc19 has been submitted as an update for Fedora 19.
libinfinity-0.5.5-1.fc20 has been submitted as an update for Fedora 20.
* 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 libinfinity-0.5.5-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
libinfinity-0.5.5-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
libinfinity-0.5.5-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Why didn't this issue receive a CVE?
(In reply to Paul Wise (Debian) from comment #6)
> Why didn't this issue receive a CVE?
I assumed this would happen by upstream or the security response team. I sent a mail to MITRE to request a CVE now.
In general it is best to send CVE requests for public issues in FLOSS to the oss-security list.
(In reply to Paul Wise (Debian) from comment #8)
> In general it is best to send CVE requests for public issues in FLOSS to the
> oss-security list.
I will remember it for the next time. This is now tracked as CVE-2014-2910.