# CVE-2023-24205: Missing authorization in n/a

> Attackers can achieve remote code execution by overwriting the configuration file due to improper access controls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2023
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-rq24-vhfq-6v9x

## What is CVE-2023-24205?

CVE-2023-24205 is a critical missing authorization vulnerability in n/a, published on 23 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Clash for Windows v0.20.12 was discovered to contain a remote code execution (RCE) vulnerability which is exploited via overwriting the configuration file (cfw-setting.yaml).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2023-24205?

It affects 1 product.


Products: Clash Project Clash.

## How do I fix CVE-2023-24205?

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

## Is CVE-2023-24205 being exploited?

There is no known exploitation of CVE-2023-24205 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2022-26255](https://insights.sbomify.com/CVE-2022-26255/): Cross-site scripting in n/a (critical 9.8)
- [CVE-2020-24772](https://insights.sbomify.com/CVE-2020-24772/): Server-side request forgery in n/a (high 8.8)
- [CVE-2022-40126](https://insights.sbomify.com/CVE-2022-40126/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24205 and fix it if it is affected.

What it is: CVE-2023-24205 is a critical missing authorization vulnerability in n/a, published on 23 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24205 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2023-24205/ (Markdown: https://insights.sbomify.com/CVE-2023-24205/index.md)
```

## Sources

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

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