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-all. 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.
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=1480656 # Description of your update notes=Security fix for [PUT CVEs HERE] # 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 web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
To be honest, I do not see any (security) problem here. If the audio file header is corrupted, oggenc simply cannot cannot open the file. From user's perspective it does not really matter whether the process is terminated by exit() or by the kernel handling a NULL pointer dereference. Please clarify what exactly is your concern here.
The fact that it terminates via a NULL pointer dereference means that someone can crash it from another process. Thats probably why it got a CVE and why its a security issue. As this already has a CVE, I we can't do anything else about it but feel free to close it of you think you should.
I believe this was fixed in vorbis-tools-1.4.0-14.fc20, so I am closing the bug as CURRENTRELEASE. Please feel free to reopen if you are still able to trigger the crash.