Red Hat Bugzilla – Bug 866567
CVE-2012-4522 ruby: unintentional file creation caused by inserting an illegal NUL character [fedora-all]
Last modified: 2012-10-24 11:27:24 EDT
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
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:
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
Bodhi update submission link:
F-18 F-17: already in queue
F-16 seems unaffected (I cannot reproduce this). Can someone confirm this?
I cannot reproduce with F16, so F16 should be OK.
@Mamoru: Could you please reference this bug in Bodhi updates? Thank you.
(In reply to comment #4)
> @Mamoru: Could you please reference this bug in Bodhi updates? Thank you.
I don't want to edit bodhi requests which were already pushed into testing, because bodhi shows warnings like "Adding or removing builds from this update will move it back to a pending state" (this does not say about only editing comments, however I am not sure if editing comments only is really safe).
(In reply to comment #5)
OK, np ... so may be this should move into MODIFIED state at least.
This issue did not affect the version of ruby as shipped with Fedora-16.
This issue was fixed in Fedora-17, via the following security advisory:
Fixed on F-18, 17 (not affected on F-16), closing.