# CVE-2011-2263: Information disclosure in n/a

> Local attackers can exploit an unspecified vulnerability in Oracle SPARC server firmware to compromise data confidentiality.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/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:** 20 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5r9m-gfj7-vg3w

## What is CVE-2011-2263?

CVE-2011-2263 is a low-severity vulnerability in n/a, published on 20 Jul 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unspecified vulnerability in Sun Integrated Lights Out Manager in Oracle SysFW 8.0.3.b or earlier for various Oracle SPARC T3, SPARC Netra T3, Sun Blade, and Sun Fire servers allows local users to affect confidentiality via unknown vectors.

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

It affects 23 products.


Products: Oracle Netra Sparc T3-1, Oracle Sparc T3-1, Oracle Sparc T3-1b, Oracle Sparc T3-3, Oracle Sparc T3-4, Oracle Sun Blade X6250, Oracle Sun Blade X6270, Oracle Sun Blade X6270 M2, Oracle Sun Blade X6275, Oracle Sun Blade X6275 M2, Oracle Sun Blade X6440 M2, Oracle Sun Blade X6450, Oracle Sun Fire X2270, Oracle Sun Fire X2270 M2, Oracle Sun Fire X4170, Oracle Sun Fire X4170 M2, Oracle Sun Fire X4270, Oracle Sun Fire X4270 M2, Oracle Sun Fire X4275, Oracle Sun Fire X4470 and 3 more.

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

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

## Is CVE-2011-2263 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2288](https://insights.sbomify.com/CVE-2011-2288/): Other in n/a (critical 10.0)
- [CVE-2011-2307](https://insights.sbomify.com/CVE-2011-2307/): Other in n/a (high 7.5)
- [CVE-2012-3128](https://insights.sbomify.com/CVE-2012-3128/): Other in n/a (low 3.7)
- [CVE-2012-3206](https://insights.sbomify.com/CVE-2012-3206/): Information disclosure in n/a (low 2.1)
- [CVE-2011-3522](https://insights.sbomify.com/CVE-2011-3522/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2263 is a low-severity vulnerability in n/a, published on 20 Jul 2011. 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-2011-2263 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-2263/ (Markdown: https://insights.sbomify.com/CVE-2011-2263/index.md)
```

## Sources

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

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