# CVE-2017-14704: File upload in n/a

> Authenticated attackers can upload malicious files with executable extensions to achieve arbitrary code execution on the server.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-64w2-f474-7rh8

## What is CVE-2017-14704?

CVE-2017-14704 is a high-severity vulnerability in n/a, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple unrestricted file upload vulnerabilities in the (1) imageSubmit and (2) proof_submit functions in Claydip Laravel Airbnb Clone 1.0 allow remote authenticated users to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in images/profile.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2017-14704?

It affects 1 product.


Products: Claydip Airbnb Clone.

## How do I fix CVE-2017-14704?

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

## Is CVE-2017-14704 being exploited?

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

Public exploit code:

- Claydip Airbnb Clone 1.0 - Arbitrary File Upload (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14704 and fix it if it is affected.

What it is: CVE-2017-14704 is a high-severity vulnerability in n/a, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14704 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-2017-14704/ (Markdown: https://insights.sbomify.com/CVE-2017-14704/index.md)
```

## Sources

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

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