# CVE-2014-1827: File upload in n/a

> Remote attackers can upload arbitrary files via null byte injection in the WiFi Transfer feature, potentially leading to code execution.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 26 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6pwx-x4rc-c5mx

## What is CVE-2014-1827?

CVE-2014-1827 is a medium-severity vulnerability in n/a, published on 26 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The iThoughtsHD app 4.19 for iOS on iPad devices, when the WiFi Transfer feature is used, allows remote attackers to upload arbitrary files by placing a %00 sequence after a dangerous extension, as demonstrated by a .html%00.txt file.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2014-1827?

It affects 1 product.


Products: Ithoughts Ithoughtshd.

## How do I fix CVE-2014-1827?

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

## Is CVE-2014-1827 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1828](https://insights.sbomify.com/CVE-2014-1828/): Denial of service in n/a (medium 4.3)
- [CVE-2014-1826](https://insights.sbomify.com/CVE-2014-1826/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1827 and fix it if it is affected.

What it is: CVE-2014-1827 is a medium-severity vulnerability in n/a, published on 26 Mar 2014. 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-2014-1827 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-2014-1827/ (Markdown: https://insights.sbomify.com/CVE-2014-1827/index.md)
```

## Sources

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

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