# CVE-2017-7552: Code injection in n/a

> An attacker can execute arbitrary files via the file editor in RHMAP Core, compromising source control projects and other users.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jc66-7vpm-57fw

## What is CVE-2017-7552?

CVE-2017-7552 is a critical code injection vulnerability in n/a, published on 28 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was discovered in the file editor of millicore, affecting versions before 3.19.0 and 4.x before 4.5.0, which allows files to be executed as well as created. An attacker could use this flaw to compromise other users or teams projects stored in source control management of the RHMAP Core installation.

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

It affects 1 product.


Products: Redhat Mobile Application Platform.

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

Upgrade to a fixed version.

## Is CVE-2017-7552 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-7553](https://insights.sbomify.com/CVE-2017-7553/): Server-side request forgery in n/a (medium 6.3)
- [CVE-2017-7554](https://insights.sbomify.com/CVE-2017-7554/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7552 is a critical code injection vulnerability in n/a, published on 28 Sep 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-7552 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-7552/ (Markdown: https://insights.sbomify.com/CVE-2017-7552/index.md)
```

## Sources

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

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