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.

Weaknesses 1

References 2

• github.com https://github.com/honojs/hono/security/advisories/GHSA-26pp-8wgv-hjvm
• vulncheck.com https://www.vulncheck.com/advisories/hono-missing-cookie-name-validation-in-setcookie

Remediation