Hono, a web framework, prior to version 4.6.5 is vulnerable to bypass of cross-site request forgery (CSRF) middleware by a request without Content-Type header. Although the CSRF middleware verifies the Content-Type Header, Hono always considers a request without a Content-Type header to be safe. This can allow an attacker to bypass CSRF protection implemented with Hono CSRF middleware. Version 4.6.5 fixes this issue.
Metrics
Affected Vendors & Products
References
History
Thu, 07 Nov 2024 18:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Title | Honor vulnerable to bypass of CSRF Middleware by a request without Content-Type header. | Hono vulnerable to bypass of CSRF Middleware by a request without Content-Type header. |
Tue, 15 Oct 2024 17:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Hono
Hono hono |
|
CPEs | cpe:2.3:a:hono:hono:*:*:*:*:*:node.js:*:* | |
Vendors & Products |
Hono
Hono hono |
|
Metrics |
ssvc
|
Tue, 15 Oct 2024 16:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | Hono, a web framework, prior to version 4.6.5 is vulnerable to bypass of cross-site request forgery (CSRF) middleware by a request without Content-Type header. Although the CSRF middleware verifies the Content-Type Header, Hono always considers a request without a Content-Type header to be safe. This can allow an attacker to bypass CSRF protection implemented with Hono CSRF middleware. Version 4.6.5 fixes this issue. | |
Title | Honor vulnerable to bypass of CSRF Middleware by a request without Content-Type header. | |
Weaknesses | CWE-352 | |
References |
| |
Metrics |
cvssV3_1
|
MITRE
Status: PUBLISHED
Assigner: GitHub_M
Published: 2024-10-15T15:56:14.408Z
Updated: 2024-11-07T18:33:39.270Z
Reserved: 2024-10-09T22:06:46.171Z
Link: CVE-2024-48913
Vulnrichment
Updated: 2024-10-15T16:15:37.945Z
NVD
Status : Awaiting Analysis
Published: 2024-10-15T16:15:05.960
Modified: 2024-10-16T16:38:43.170
Link: CVE-2024-48913
Redhat
No data.