Crass: Non-ASCII characters cause superlinear CPU consumption
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| rgrove | crass | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Rgrove | Crass |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8vfg-2r28-hvhj | Crass: Non-ASCII characters cause superlinear CPU consumption |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.486% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-770 | |
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rgrove
Rgrove crass |
|
| Vendors & Products |
Rgrove
Rgrove crass |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Crass: Non-ASCII characters cause superlinear CPU consumption | |
| Weaknesses | CWE-400 | |
| References |
| |
| Metrics |
cvssV4_0
|