# CVE-2018-12528: File upload in n/a

> Attackers can upload malicious files via the backup restore feature on Intex N150 routers, potentially executing code or causing denial of service.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 2 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c8gg-gqhg-8j49

## What is CVE-2018-12528?

CVE-2018-12528 is a high-severity vulnerability in n/a, published on 2 Jul 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Intex N150 devices. The backup/restore option does not check the file extension uploaded for importing a configuration files backup, which can lead to corrupting the router firmware settings or even the uploading of malicious files. In order to exploit the vulnerability, an attacker can upload any malicious file and force reboot the router with it.

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

## Which versions are affected by CVE-2018-12528?

It affects 1 product.


Products: Intex N150 Firmware.

## How do I fix CVE-2018-12528?

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

## Is CVE-2018-12528 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12529](https://insights.sbomify.com/CVE-2018-12529/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12528 and fix it if it is affected.

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

## Sources

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

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