# CVE-2011-2260: Other in n/a

> Remote attackers can compromise confidentiality and integrity of Oracle GlassFish Server administration components.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3f5f-g8gg-c73f

## What is CVE-2011-2260?

CVE-2011-2260 is a medium-severity vulnerability in n/a, published on 20 Jul 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unspecified vulnerability in the Oracle GlassFish Server component in Oracle Sun Products Suite 2.1.1 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Administration.

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

It affects 1 product.


Products: Oracle Sun Products Suite.

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

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

## Is CVE-2011-2260 being exploited?

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

Public exploit code:

- Oracle Sun GlassFish Enterprise Server - Persistent Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0888](https://insights.sbomify.com/CVE-2010-0888/): Other in n/a (critical 10.0)
- [CVE-2012-0208](https://insights.sbomify.com/CVE-2012-0208/): Other in n/a (critical 9.0)
- [CVE-2011-3517](https://insights.sbomify.com/CVE-2011-3517/): Denial of service in n/a (high 7.8)
- [CVE-2011-2310](https://insights.sbomify.com/CVE-2011-2310/): Other in n/a (high 7.5)
- [CVE-2011-2245](https://insights.sbomify.com/CVE-2011-2245/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2260 is a medium-severity vulnerability in n/a, published on 20 Jul 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2260 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-2260/ (Markdown: https://insights.sbomify.com/CVE-2011-2260/index.md)
```

## Sources

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

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