# CVE-2012-2963: Missing authorization in n/a

> Remote attackers can access sensitive information via an unauthenticated script in the BreakingPoint Storm appliance web interface.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-66vh-4g4j-7x2q

## What is CVE-2012-2963?

CVE-2012-2963 is a medium-severity missing authorization vulnerability in n/a, published on 12 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The administrative interface in the embedded web server on the BreakingPoint Storm appliance before 3.0 does not require authentication for the gwt/BugReport script, which allows remote attackers to obtain sensitive information by downloading a .tgz file.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-2963?

It affects 2 products.


Products: Breakingpointsystems Breakingpoint Storm Appliance, Breakingpointsystems Breakingpoint Storm Appliance Ctm.

## How do I fix CVE-2012-2963?

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

## Is CVE-2012-2963 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2964](https://insights.sbomify.com/CVE-2012-2964/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2963 and fix it if it is affected.

What it is: CVE-2012-2963 is a medium-severity missing authorization vulnerability in n/a, published on 12 Aug 2012. 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-2012-2963 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-2012-2963/ (Markdown: https://insights.sbomify.com/CVE-2012-2963/index.md)
```

## Sources

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

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