# CVE-2019-10012: File upload in n/a

> Remote attackers can upload and execute arbitrary ASPX code via the MoxieManager plugin, leading to full system compromise.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** 25 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ppjq-m4gx-9pj8

## What is CVE-2019-10012?

CVE-2019-10012 is a high-severity vulnerability in n/a, published on 25 Mar 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenzabar JICS (aka Internet Campus Solution) before 9 allows remote attackers to upload and execute arbitrary .aspx code by placing it in a ZIP archive and using the MoxieManager (for .NET) plugin before 2.1.4 in the moxiemanager directory within the installation folder ICS\ICS.NET\ICSFileServer.

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

## Which versions are affected by CVE-2019-10012?

It affects 2 products.


Products: Jenzabar Internet Campus Solution, Tiny Moxiemanager.

## How do I fix CVE-2019-10012?

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

## Is CVE-2019-10012 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8434](https://insights.sbomify.com/CVE-2020-8434/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2019-10011](https://insights.sbomify.com/CVE-2019-10011/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10012 and fix it if it is affected.

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

## Sources

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

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