Microdot: HTTP response splitting in Response.set_cookie()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| miguelgrinberg | microdot | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Miguelgrinberg | Microdot |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-7wc8-wvc4-m498 | Microdot has HTTP response splitting in Response.set_cookie() |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.215% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Miguelgrinberg
Miguelgrinberg microdot |
|
| Vendors & Products |
Miguelgrinberg
Miguelgrinberg microdot |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Microdot is a minimalistic Python web framework. Prior to 2.6.1, the Response.set_cookie() method does not sanitize its string arguments, and in particular will not detect the presence of the \r\n sequence in them. This can be a potential source of header injection attacks. For a header injection attack through this issue to be possible, an attacker must first infiltrate the client (for example through an independent XSS attack), so that it can send malicious information that is destined to be stored in a cookie by the server on behalf of the victim. An attacker that infiltrates one client can only orchestrate a header injection attack for that client, all other clients that were not infiltrated are safe. This vulnerability is fixed in 2.6.1. | |
| Title | Microdot: HTTP response splitting in Response.set_cookie() | |
| Weaknesses | CWE-113 | |
| References |
| |
| Metrics |
cvssV3_1
|