# CVE-2011-2584: Missing authorization in n/a

> Remote attackers can access administrative pages to cause denial of service or obtain sensitive information due to missing authorization checks.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-fg5w-cxx4-22vf

## What is CVE-2011-2584?

CVE-2011-2584 is a high-severity missing authorization vulnerability in n/a, published on 20 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Show and Share 5(2), 5.2(1), and 5.2(2) before 5.2(2.1) allows remote attackers to access the (1) Encoders and Pull Configurations, (2) Push Configurations, (3) Video Encoding Formats, and (4) Transcoding administration pages, and cause a denial of service (live event outage) or obtain potentially sensitive information, via unspecified vectors, aka Bug ID CSCto73758.

Weakness: CWE-264

## Which versions are affected by CVE-2011-2584?

It affects 1 product.


Products: Cisco Show and Share.

## How do I fix CVE-2011-2584?

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

## Is CVE-2011-2584 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2585](https://insights.sbomify.com/CVE-2011-2585/): Code injection in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2584 and fix it if it is affected.

What it is: CVE-2011-2584 is a high-severity missing authorization vulnerability in n/a, published on 20 Oct 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2584 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-2011-2584/ (Markdown: https://insights.sbomify.com/CVE-2011-2584/index.md)
```

## Sources

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

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