Crass: A large number of adjacent CSS comments can trigger a SystemStackError
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-wwpr-jff3-395c | Crass: A large number of adjacent CSS comments can trigger a SystemStackError |
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 the `:preserve_comments` option is not enabled, which is the default, Crass discards CSS comments by recursively consuming the next token. An attacker-provided stylesheet containing a very large number of adjacent comments can cause excessive recursion and trigger a `SystemStackError`, denying service to the parsing application. Preserving comments avoids this recursive path. This issue is fixed in version 1.0.7. | |
| Title | Crass: A large number of adjacent CSS comments can trigger a SystemStackError | |
| Weaknesses | CWE-674 | |
| References |
| |
| Metrics |
cvssV4_0
|