Bug 1980330 - CVE-2021-31799 rubygem-rdoc: Command injection vulnerability in RDoc [fedora-all]
Summary: CVE-2021-31799 rubygem-rdoc: Command injection vulnerability in RDoc [fedora-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-rdoc
Version: 34
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: mo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2021-31799
TreeView+ depends on / blocked
 
Reported: 2021-07-08 11:52 UTC by Tomas Hoger
Modified: 2021-09-02 11:09 UTC (History)
4 users (show)

Fixed In Version: rubygem-rdoc-6.3.2-201.fc36
Clone Of:
Environment:
Last Closed: 2021-09-02 11:09:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Tomas Hoger 2021-07-08 11:52:17 UTC
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.

Comment 1 Tomas Hoger 2021-07-08 11:52:24 UTC
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

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1980132,1980330

# 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

Comment 2 Tomas Hoger 2021-07-08 12:02:03 UTC
I'm not entirely sure why we still have rubygem-rdoc as a separate component.  Binary packages built from this component do not seem to get shipped, it seems only binary packages from the rdoc bundled in ruby are shipped, as those currently provide newer version.  However, the rubygems-rdoc source rpm is still included in the repos.

Comment 3 Vít Ondruch 2021-07-27 12:50:06 UTC
(In reply to Tomas Hoger from comment #2)
> I'm not entirely sure why we still have rubygem-rdoc as a separate
> component.  Binary packages built from this component do not seem to get
> shipped, it seems only binary packages from the rdoc bundled in ruby are
> shipped, as those currently provide newer version.  However, the
> rubygems-rdoc source rpm is still included in the repos.

We sometimes update the independent rubygem-rdoc. The higher NVR wins and currently it might be the ruby subpackage.

Comment 4 Fedora Update System 2021-09-02 11:07:17 UTC
FEDORA-2021-9a96dfe618 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2021-9a96dfe618

Comment 5 Fedora Update System 2021-09-02 11:09:56 UTC
FEDORA-2021-9a96dfe618 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.