# CVE-2017-12290: Cross-site scripting in Cisco Registered Envelope Service

> Unauthenticated attackers can execute arbitrary scripts or redirect users via XSS in the Cisco Registered Envelope Service web interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c793-vmwj-5h59

## What is CVE-2017-12290?

CVE-2017-12290 is a medium-severity cross-site scripting vulnerability in Cisco Registered Envelope Service, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple vulnerabilities in the web interface of the Cisco Registered Envelope Service (a cloud-based service) could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack or redirect a user of the affected service to an undesired web page. The vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface of the affected service. An attacker could exploit these vulnerabilities by persuading a user to click a malicious link or by sending an HTTP request that could cause the affected service to redirect the request to a specified malicious URL. A successful exploit could allow the attacker to execute arbitrary script code in the context of the web interface of the affected system or allow the attacker to access sensitive browser-based information on the affected system. These types of exploits could also be used in phishing attacks that send users to malicious websites without their knowledge. Cisco Bug IDs: CSCve77195, CSCve90978, CSCvf42310, CSCvf42703, CSCvf42723, CSCvf46169, CSCvf49999.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Cisco Email Encryption.

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

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

## Is CVE-2017-12290 being exploited?

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

## Other vulnerabilities in Cisco Registered Envelope Service

- [CVE-2017-12291](https://insights.sbomify.com/CVE-2017-12291/): Cross-site scripting in Cisco Registered Envelope Service (medium 6.1)
- [CVE-2017-12292](https://insights.sbomify.com/CVE-2017-12292/): Cross-site scripting in Cisco Registered Envelope Service (medium 6.1)
- [CVE-2017-12322](https://insights.sbomify.com/CVE-2017-12322/): Cross-site scripting in Cisco Registered Envelope Service (medium 6.1)
- [CVE-2018-0208](https://insights.sbomify.com/CVE-2018-0208/): Cross-site scripting in Cisco Registered Envelope Service (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12290 is a medium-severity cross-site scripting vulnerability in Cisco Registered Envelope Service, published on 16 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12290 in the wild and no public exploit code.

Affected product: Cisco Registered Envelope Service. 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-12290/ (Markdown: https://insights.sbomify.com/CVE-2017-12290/index.md)
```

## Sources

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

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