Hono - Missing Cookie Name Validation in setCookie()
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hono | Hono | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Hono | Hono |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-26pp-8wgv-hjvm | Hono missing validation of cookie name on write path in setCookie() |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.418% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-113 | CWE-20 |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hono before 4.12.12 does not validate cookie names on the write path in the setCookie(), serialize(), and serializeSigned() functions, allowing invalid characters such as control characters (e.g. \r or \n) when an application passes a user-controlled cookie name. This can produce malformed Set-Cookie header values. In modern runtimes such as Node.js and Cloudflare Workers, such invalid header values are rejected and cause a runtime error before the response is sent, so header injection or response splitting could not be reproduced; the issue primarily affects correctness and robustness, resulting in runtime errors (availability) rather than confirmed header injection. | |
| Title | Hono - Missing Cookie Name Validation in setCookie() | |
| First Time appeared |
Hono
Hono hono |
|
| Weaknesses | CWE-113 | |
| CPEs | cpe:2.3:a:hono:hono:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Hono
Hono hono |
|
| References |
| |
| Metrics |
cvssV3_1
|