Doggo vulnerable to cross-site scripting via unescaped date field values
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 0.14.8 and 0161c976a114a4a4faee22d599b3fd5f147fc443.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in woylie doggo allows Reflected XSS. Doggo.normalize_value/2 in lib/doggo.ex returned date field values wrapped in {:safe, ...}, the Phoenix.HTML marker meaning "already escaped, emit verbatim", without escaping them, so the value reached the value attribute of the <input> rendered by the field component unchanged. Any application rendering <.field type="date"> over user-controlled params is affected through the ordinary Phoenix form round-trip, where a failed validation re-renders the submitted value. The pattern kept exactly the first ten bytes and discarded shorter values, capping a payload at ten bytes: enough to terminate the attribute and open an element or attach a short event handler, not enough to place attacker-chosen script inline. Only type="date" is affected. This issue affects doggo: from 0.1.0 before 0.14.8.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| woylie | >=0.1.0 <0.14.8, >=ae65fed72982ec97f95af931686c627b19c2b58d <0161c976a114a4a4faee22d599b3fd5f147fc443 | 0.14.8, 0161c976a114a4a4faee22d599b3fd5f147fc443 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket