Crass: Non-ASCII characters cause superlinear CPU consumption
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in crass 1.0.7.
Crass is a Ruby CSS parser that's fully compliant with the CSS Syntax Level 3 specification. Prior to 1.0.7, when Crass parses input containing `non-ASCII characters`, inefficiencies in tracking the positions of `multi-byte characters` result in superlinear parsing time. An attacker-controlled CSS input consisting of many `non-ASCII characters` can therefore cause excessive CPU consumption and potentially denial of service. This issue is fixed in version 1.0.7.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| rgrove | <1.0.7 | ||
| rubygems: crass | <1.0.7 | 1.0.7 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in crass (RubyGems), strongest first
Embed
A live severity badge for an advisory, README or ticket