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-19 tracking bug for drupal6-freelinking: see blocks bug list for full details of the security issue(s). [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=1127519,1127520 # Description of your update notes=Security fix for CVE-2014-5179 # 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=1127519,1127520
According to upstream (https://www.drupal.org/project/freelinking): This module is unsupported due to a security issue the maintainer didn’t fix. See SA-CONTRIB-2014-072 - Freelinking, Freelinking Case Tracker - Access bypass (https://www.drupal.org/node/2308503) for details. I retired this package on f21, rawhide, el5, and el6. f19 and f20 gave me the following errors though: > Could not retire package: You are not allowed to retire the package: drupal6-freelinking on branch f19. > ERROR:rpkg:Could not retire package: You are not allowed to retire the package: drupal6-freelinking on branch f19. > Could not retire package: You are not allowed to retire the package: drupal6-freelinking on branch f20. > ERROR:rpkg:Could not retire package: You are not allowed to retire the package: drupal6-freelinking on branch f20. I am listed in pkgdb as the main contact, an admin, a committer, and a watcher of this package. Do I need to submit a ticket to get this pkg retired on f19 and f20 or can you do it?
Adding Eric to Cc. Eric, can you please help with the above?
Sorry for the delay. I'm look at this now.
The word from Release Engineering is that once the package has been shipped it cannot be pulled back. Your current choices are: 1. Ship a fix. 2. Ship an updated package that removes the executable and replaces all the pieces with a README. 3. Orphan the package. 4. Blog about it/otherwise get the word out that this package is bad. Obviously, these are not mutually exclusive. You may select to do a bunch of these. I wish I had a better option.
What ever happened with this update? If this package won't be updated I'd highly recommend you orphan it now before the release of F21.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
(In reply to Eric Christensen from comment #6) > What ever happened with this update? If this package won't be updated I'd > highly recommend you orphan it now before the release of F21. Per comment #2, I retired this package on f21, rawhide, el5, and el6. I just orphaned f19 and f20.
Package retired/orphaned