# CVE-2011-2680: Unspecified vulnerability in IBM Rational DOORS Web Access 1.4.x before 1.4.0.4 has unknown impact and remote attack vectors related to the


- **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:** 7 Jul 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5rgv-j3xf-4664

## What is CVE-2011-2680?

CVE-2011-2680 is a critical vulnerability in n/a, published on 7 Jul 2011. 

### Official description

Unspecified vulnerability in IBM Rational DOORS Web Access 1.4.x before 1.4.0.4 has unknown impact and remote attack vectors related to the "server error response."

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

It affects 1 product.


Products: Ibm Rational Doors Web Access.

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

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

## Is CVE-2011-2680 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2681](https://insights.sbomify.com/CVE-2011-2681/): Other in n/a (critical 10.0)
- [CVE-2018-1975](https://insights.sbomify.com/CVE-2018-1975/): Cross-site scripting in Rational DOORS Web Access (medium 5.4)
- [CVE-2011-2679](https://insights.sbomify.com/CVE-2011-2679/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2011-2682](https://insights.sbomify.com/CVE-2011-2682/): Denial of service in n/a (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2680 is a critical vulnerability in n/a, published on 7 Jul 2011. 
Exploitation: There is no known exploitation of CVE-2011-2680 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-2680/ (Markdown: https://insights.sbomify.com/CVE-2011-2680/index.md)
```

## Sources

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

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