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

> Attackers can write arbitrary content to configuration files to upload a webshell, enabling remote code execution on Codiad installations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **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 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hjgm-hqw5-jg63

## What is CVE-2017-1000125?

CVE-2017-1000125 is a high-severity vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Codiad(full version) is vulnerable to write anything to configure file in the installation resulting upload a webshell.

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

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

It affects 1 product.


Products: Codiad Codiad.

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

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

## Is CVE-2017-1000125 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19208](https://insights.sbomify.com/CVE-2019-19208/): Code injection in codiad (critical 9.8)
- [CVE-2018-14009](https://insights.sbomify.com/CVE-2018-14009/): Codiad remote code execution vulnerability (critical 9.8)
- [CVE-2017-11366](https://insights.sbomify.com/CVE-2017-11366/): Codiad Vulnerable to Shell Command Injection (critical 9.8)
- [CVE-2020-14043](https://insights.sbomify.com/CVE-2020-14043/): Codiad CSRF Vulnerability (high 8.8)
- [CVE-2020-23355](https://insights.sbomify.com/CVE-2020-23355/): Codiad Vulnerable to PHP Magic Hash Vulnerability (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-1000125 is a high-severity vulnerability in n/a, published on 17 Nov 2017. 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-2017-1000125 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-1000125/ (Markdown: https://insights.sbomify.com/CVE-2017-1000125/index.md)
```

## Sources

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

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