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

> Authenticated users with Monitor-Only role can bypass restrictions to modify system configuration in Cisco CG-NMS.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:N/I:P/A:N`)
- **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:** 10 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wh7v-9p3v-c89w

## What is CVE-2015-6362?

CVE-2015-6362 is a medium-severity missing authorization vulnerability in n/a, published on 10 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The web GUI in Cisco Connected Grid Network Management System (CG-NMS) 3.0(0.35) and 3.0(0.54) allows remote authenticated users to bypass intended access restrictions and modify the configuration by leveraging the Monitor-Only role, aka Bug ID CSCuw42640.

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Connected Grid Network Management System.

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

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

## Is CVE-2015-6362 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6780](https://insights.sbomify.com/CVE-2017-6780/): Denial of service in Cisco IoT Field Network Director (high 7.5)
- [CVE-2013-1163](https://insights.sbomify.com/CVE-2013-1163/): SQL injection in n/a (high 7.5)
- [CVE-2013-1171](https://insights.sbomify.com/CVE-2013-1171/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6362 is a medium-severity missing authorization vulnerability in n/a, published on 10 Nov 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6362 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-6362/ (Markdown: https://insights.sbomify.com/CVE-2015-6362/index.md)
```

## Sources

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

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