# CVE-2024-41657: GHSL-2024-035: Casdoor CORS misconfiguration

> Attackers can bypass CORS restrictions to make cross-origin requests as a logged-in user, potentially leading to account takeover or data theft.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Aug 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-mchx-7j67-8mcf, GO-2024-3087

## What is CVE-2024-41657?

CVE-2024-41657 is a high-severity vulnerability in casdoor, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Casdoor is a UI-first Identity and Access Management (IAM) / Single-Sign-On (SSO) platform. In Casdoor 1.577.0 and earlier, a logic vulnerability exists in the beego filter CorsFilter that allows any website to make cross domain requests to Casdoor as the logged in user. Due to the a logic error in checking only for a prefix when authenticating the Origin header, any domain can create a valid subdomain with a valid subdomain prefix (Ex: localhost.example.com), allowing the website to make requests to Casdoor as the current signed-in user.

Weakness: CWE-697 (Incorrect Comparison), CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

## Which versions are affected by CVE-2024-41657?

3 open source packages ship an affected version, including github.com/casdoor/casdoor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/casdoor/casdoor` | Go | All versions | None |
| `github.com/casdoor/casdoor` | Go | All versions to 1.557.0 | None |
| `github.com/casdoor/casdoor` | Go | All versions to 1.557.0 | None |

Products: Casbin Casdoor.

## How do I fix CVE-2024-41657?

No fix has been published for CVE-2024-41657 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41657 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41657 exists.

## Other vulnerabilities in casdoor

- [CVE-2022-38638](https://insights.sbomify.com/CVE-2022-38638/): Casdoor arbitrary file write vulnerability (critical 9.1)
- [CVE-2022-44942](https://insights.sbomify.com/CVE-2022-44942/): Casdoor arbitrary file deletion vulnerability via uploadFile function (high 8.1)
- [CVE-2024-41264](https://insights.sbomify.com/CVE-2024-41264/): casdoor's use of`ssh.InsecureIgnoreHostKey()` disables host key verification (high 7.5)
- [CVE-2022-24124](https://insights.sbomify.com/CVE-2022-24124/): SQL Injection in Casdoor (high 7.5)
- [CVE-2023-34927](https://insights.sbomify.com/CVE-2023-34927/): Casdoor Cross-Site Request Forgery vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41657 and fix it if it is affected.

What it is: CVE-2024-41657 is a high-severity vulnerability in casdoor, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41657 exists.

Affected packages and fixed versions:
- github.com/casdoor/casdoor (Go): affected all versions; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions up to 1.557.0; no fix listed
- github.com/casdoor/casdoor (Go): affected all versions up to 1.557.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41657/ (Markdown: https://insights.sbomify.com/CVE-2024-41657/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41657
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41657
- OSV: https://osv.dev/vulnerability/CVE-2024-41657

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41657/
Summaries are generated and may contain mistakes; the official description above is the record.