# CVE-2015-6265: Missing authorization in n/a

> Local users can bypass access restrictions to read or write files on Cisco ACE devices via a crafted CLI command.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-frj5-6v5r-wvhp

## What is CVE-2015-6265?

CVE-2015-6265 is a medium-severity missing authorization vulnerability in n/a, published on 27 Aug 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The CLI in Cisco Application Control Engine (ACE) 4700 A5 3.0 and earlier allows local users to bypass intended access restrictions, and read or write to files, by entering an unspecified CLI command with a crafted file as this command's input, aka Bug ID CSCur23662.

Weakness: CWE-264

## Which versions are affected by CVE-2015-6265?

It affects 1 product.


Products: Cisco Application Control Engine 4700.

## How do I fix CVE-2015-6265?

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

## Is CVE-2015-6265 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6265 and fix it if it is affected.

What it is: CVE-2015-6265 is a medium-severity missing authorization vulnerability in n/a, published on 27 Aug 2015. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6265 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-2015-6265/ (Markdown: https://insights.sbomify.com/CVE-2015-6265/index.md)
```

## Sources

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

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