Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1024650
| Summary: | CVE-2013-4479 rubygem-sup: command injection flaw in content type handling [fedora-all] | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Murray McAllister <mmcallis> |
| Component: | rubygem-sup | Assignee: | Praveen Kumar <kumarpraveen.nitdgp> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 21 | CC: | jrusnack, kumarpraveen.nitdgp, pj.pandit, shreyankg, sparks |
| Target Milestone: | --- | Keywords: | Reopened, Security, SecurityTracking |
| Target Release: | --- | Flags: | shreyankg:
needinfo+
shreyankg: needinfo+ shreyankg: needinfo+ |
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | fst_ping=3,fst_owner=pjp | ||
| Fixed In Version: | Doc Type: | Release Note | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-02 03:01:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1224028 | ||
| Bug Blocks: | |||
|
Description
Murray McAllister
2013-10-30 07:19:27 UTC
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=1024647,1024650 Hello shreyankg, Could you please fix this soon? This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above. 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. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. Can you please push a fix for this package? Can an update be pushed for this package? If I don't receive a response by Monday I'll start a non-responsive maintainer process for this package. (In reply to Eric Christensen from comment #7) > Can an update be pushed for this package? > > If I don't receive a response by Monday I'll start a non-responsive > maintainer process for this package. Please don't do that. I have added Praveen Kumar, who has agreed to be the co-maintainer for sup. (In reply to Shreyank Gupta from comment #8) > (In reply to Eric Christensen from comment #7) > > Can an update be pushed for this package? > > > > If I don't receive a response by Monday I'll start a non-responsive > > maintainer process for this package. > > Please don't do that. > I have added Praveen Kumar, who has agreed to be the co-maintainer for sup. I will update this package soon with latest release. Awesome! rubygem-sup-0.21.0-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/rubygem-sup-0.21.0-1.fc22 rubygem-sup-0.21.0-1.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/rubygem-sup-0.21.0-1.fc21 Package rubygem-sup-0.21.0-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing rubygem-sup-0.21.0-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-7393/rubygem-sup-0.21.0-1.fc22 then log in and leave karma (feedback). Can this be pushed to stable now? It seems to have been in testing for a while. Also, can you push this fix to F20 as well? (In reply to Eric Christensen from comment #14) > Can this be pushed to stable now? It seems to have been in testing for a > while. Also, can you push this fix to F20 as well? There was a dependency update and I created a review request for it, once it's done will update it. ruby-ncurses-1.3.1-16.fc23 rubygem-sup-0.21.0-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14929 ruby-ncurses-1.3.1-16.fc23, rubygem-sup-0.21.0-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update rubygem-sup ruby-ncurses'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14929 ruby-ncurses-1.3.1-16.fc23, rubygem-sup-0.21.0-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora 'version' of '21'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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 this bug is closed as described in the policy above. 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. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |