Alerts This Week
Warning Icon 1 1,153
Alerts This Week
Warning Icon 1 1,153

Gentoo: GLSA 202401-14 Low Severity: RedCloth ReDoS Attack

gentoo
Calendar Grey January 10, 2024
Dist Gentoo Esm H88
A critical flaw affecting RedCloth has been reported in Gentoo GLSA 202401-15; users are advised to upgrade without delay.
A denial of service vulnerability has been found in RedCloth.

Summary

A vulnerability has been discovered in RedCloth. Please review the CVE identifier referenced below for details.

Topics%20covered

Topics Covered

security advisory denial of service Gentoo vulnerability low severity RedCloth

Resolution

All RedCloth users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-ruby/redcloth-4.3.2-r5"

References

[ 1 ] CVE-2023-31606 https://nvd.nist.gov/vuln/detail/CVE-2023-31606

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website:
https://security.gentoo.org/glsa/202401-14
style>.gentoo_availability{display:block;}

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.

Severity
low
Lowest
Low
Medium
High
Critical

Severity: Low
Title: RedCloth: ReDoS Vulnerability
Date: January 10, 2024
Bugs: #908035
ID: 202401-14

Topics%20covered

Topics Covered

security advisory denial of service Gentoo vulnerability low severity RedCloth

Synopsis

A denial of service vulnerability has been found in RedCloth.

Background

RedCloth is a module for using Textile in Ruby

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

Package Vulnerable Unaffected ----------------- ------------ ------------ dev-ruby/redcloth < 4.3.2-r5 >= 4.3.2-r5

Impact

RedCloth is vulnerable to a regular expression denial of service ("ReDoS") attack via the sanitize_html function.

Workaround

There is no known workaround at this time.

Your message here