withastro up to 4.16.16 security.checkOrigin cross-site request forgery

Summaryinfo

A vulnerability, which was classified as problematic, has been found in withastro astro up to 4.16.16. This impacts an unknown function. Performing a manipulation of the argument security.checkOrigin results in cross-site request forgery. This vulnerability is identified as CVE-2024-56140. The attack can be initiated remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in withastro astro up to 4.16.16. This affects an unknown functionality. The manipulation of the argument security.checkOrigin with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. The summary by CVE is:

Astro is a web framework for content-driven websites. In affected versions a bug in Astro’s CSRF-protection middleware allows requests to bypass CSRF checks. When the `security.checkOrigin` configuration option is set to `true`, Astro middleware will perform a CSRF check. However, a vulnerability exists that can bypass this security. A semicolon-delimited parameter is allowed after the type in `Content-Type`. Web browsers will treat a `Content-Type` such as `application/x-www-form-urlencoded; abc` as a `simple request` and will not perform preflight validation. In this case, CSRF is not blocked as expected. Additionally, the `Content-Type` header is not required for a request. This issue has been addressed in version 4.16.17 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-56140 since 12/16/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 4.16.17 eliminates this vulnerability. Applying the patch e7d14c374b9d45e27089994a4eb72186d05514de is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-3575). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• withastro

Name

• astro

Version

• 4.16.0
• 4.16.1
• 4.16.2
• 4.16.3
• 4.16.4
• 4.16.5
• 4.16.6
• 4.16.7
• 4.16.8
• 4.16.9
• 4.16.10
• 4.16.11
• 4.16.12
• 4.16.13
• 4.16.14
• 4.16.15
• 4.16.16

License

• open-source

Website

• Product: https://github.com/withastro/astro/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion