From: glsamaker@gentoo.org
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 202406-03 ] RDoc: Remote Code Cxecution
Date: Sat, 22 Jun 2024 07:32:14 -0000 [thread overview]
Message-ID: <171904153472.8.10264189092410680463@987c7955d8b1> (raw)
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 202406-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: RDoc: Remote Code Cxecution
Date: June 22, 2024
Bugs: #927565
ID: 202406-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in RDoc, which can lead to execution
of arbitrary code.
Background
==========
RDoc produces HTML and command-line documentation for Ruby projects.
Affected packages
=================
Package Vulnerable Unaffected
------------- ------------ ------------
dev-ruby/rdoc < 6.6.3.1 >= 6.6.3.1
Description
===========
A vulnerability has been discovered in RDoc. Please review the CVE
identifier referenced below for details.
Impact
======
When parsing .rdoc_options (used for configuration in RDoc) as a YAML
file, object injection and resultant remote code execution are possible
because there are no restrictions on the classes that can be restored.
When loading the documentation cache, object injection and resultant
remote code execution are also possible if there were a crafted cache.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All RDoc users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=dev-ruby/rdoc-6.6.3.1"
References
==========
[ 1 ] CVE-2024-27281
https://nvd.nist.gov/vuln/detail/CVE-2024-27281
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/202406-03
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2024 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
https://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-06-22 7:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171904153472.8.10264189092410680463@987c7955d8b1 \
--to=glsamaker@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox