# CVE-2023-43177: Deserialization in n/a

> Attackers can exploit improper object attribute modification in CrushFTP to potentially execute arbitrary code on the server.

- **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:** 17 Nov 2023
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-6wmg-7vxw-42fx

## What is CVE-2023-43177?

CVE-2023-43177 is a critical unsafe deserialization vulnerability in n/a, published on 17 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CrushFTP prior to 10.5.1 is vulnerable to Improperly Controlled Modification of Dynamically-Determined Object Attributes.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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

It affects 1 product.


Products: Crushftp Crushftp.

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

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

## Is CVE-2023-43177 being exploited?

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

Public exploit code:

- CrushFTP <= 10.5.1 Remote Code Execution. Researchers: Ryan Emmons, Evan Malamis (github_poc): https://github.com/the-emmons/CVE-2023-43177
- CrushFTP Unauthenticated RCE (metasploit)
- CrushFTP < 10.5.1 - Unauthenticated Remote Code Execution (nuclei): http/cves/2023/CVE-2023-43177.yaml

## Other vulnerabilities in n/a

- [CVE-2025-31161](https://insights.sbomify.com/CVE-2025-31161/): CrushFTP Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2024-4040](https://insights.sbomify.com/CVE-2024-4040/): CrushFTP VFS Sandbox Escape (critical 9.8, exploited in the wild)
- [CVE-2025-54309](https://insights.sbomify.com/CVE-2025-54309/): CrushFTP Unprotected Alternate Channel (critical 9.0, exploited in the wild)
- [CVE-2024-53552](https://insights.sbomify.com/CVE-2024-53552/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-14035](https://insights.sbomify.com/CVE-2017-14035/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43177 is a critical unsafe deserialization vulnerability in n/a, published on 17 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-43177 exists.

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

## Sources

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

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