# CVE-2011-2610: Unspecified vulnerability in Opera before 11.50 has unknown impact and attack vectors, related to a "moderately severe issue."


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-82f8-mpm9-wwp7

## What is CVE-2011-2610?

CVE-2011-2610 is a critical vulnerability in Opera Opera Browser, published on 1 Jul 2011. 

### Official description

Unspecified vulnerability in Opera before 11.50 has unknown impact and attack vectors, related to a "moderately severe issue."

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

It affects 1 product.


Products: Opera Opera Browser.

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

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

## Is CVE-2011-2610 being exploited?

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

## Other vulnerabilities in Opera Opera Browser

- [CVE-2013-3211](https://insights.sbomify.com/CVE-2013-3211/): Unspecified vulnerability in Opera before 12.15 has unknown impact and attack vectors, related to a "moderately severe issue." (critical 10.0)
- [CVE-2012-4145](https://insights.sbomify.com/CVE-2012-4145/): Other in n/a (critical 10.0)
- [CVE-2012-3559](https://insights.sbomify.com/CVE-2012-3559/): Other in n/a (critical 10.0)
- [CVE-2012-3561](https://insights.sbomify.com/CVE-2012-3561/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-4683](https://insights.sbomify.com/CVE-2011-4683/): Unspecified vulnerability in Opera before 11.60 has unknown impact and attack vectors, related to a "moderately severe issue." (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2610 is a critical vulnerability in Opera Opera Browser, published on 1 Jul 2011. 
Exploitation: There is no known exploitation of CVE-2011-2610 in the wild and no public exploit code.

Affected product: Opera Opera Browser. 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-2610/ (Markdown: https://insights.sbomify.com/CVE-2011-2610/index.md)
```

## Sources

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

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