# CVE-2013-2747: Security feature bypass in n/a

> Authenticated users can bypass browser restrictions to execute arbitrary commands via keyboard shortcuts in Courion Access Risk Management Suite.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-98j7-x3wp-pm3j

## What is CVE-2013-2747?

CVE-2013-2747 is a medium-severity vulnerability in n/a, published on 29 Jan 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The password reset feature in Courion Access Risk Management Suite Version 8 Update 9 allows remote authenticated users to bypass intended Internet Explorer usage restrictions and execute arbitrary commands by using keyboard shortcuts to navigate the file system and open a command prompt.

Weakness: CWE-264

## Which versions are affected by CVE-2013-2747?

It affects 1 product.


Products: Courion Access Risk Management Suite.

## How do I fix CVE-2013-2747?

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

## Is CVE-2013-2747 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2747 and fix it if it is affected.

What it is: CVE-2013-2747 is a medium-severity vulnerability in n/a, published on 29 Jan 2014. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-2747 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-2013-2747/ (Markdown: https://insights.sbomify.com/CVE-2013-2747/index.md)
```

## Sources

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

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