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

> Authenticated users with report creation rights can execute arbitrary code via BIRT templates in BMC Remedy.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** 19 May 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-vcfr-6pgp-8283

## What is CVE-2017-17677?

CVE-2017-17677 is a high-severity code injection vulnerability in n/a, published on 19 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BMC Remedy 9.1SP3 is affected by authenticated code execution. Authenticated users that have the right to create reports can use BIRT templates to run code.

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

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

It affects 1 product.


Products: Bmc Remedy Mid-Tier.

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

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

## Is CVE-2017-17677 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-34399](https://insights.sbomify.com/CVE-2024-34399/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-17674](https://insights.sbomify.com/CVE-2017-17674/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2017-17678](https://insights.sbomify.com/CVE-2017-17678/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-17675](https://insights.sbomify.com/CVE-2017-17675/): Information disclosure in n/a (medium 5.3)
- [CVE-2024-34398](https://insights.sbomify.com/CVE-2024-34398/): Cross-site scripting in n/a (medium 4.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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