# CVE-2010-2279: Security feature bypass in n/a

> Attackers can bypass SSL enforcement in IBM Lotus Connections when forced SSL is enabled, potentially exposing data or session tokens.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 14 Jun 2010
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-r5g6-h9r4-8fp4

## What is CVE-2010-2279?

CVE-2010-2279 is a high-severity vulnerability in n/a, published on 14 Jun 2010. It can be exploited over the network.

### Official description

The Top Updates implementation in the Homepage component in IBM Lotus Connections 2.5.x before 2.5.0.2, when "forced SSL" is enabled, uses http for links, which has unspecified impact and remote attack vectors.

## Which versions are affected by CVE-2010-2279?

It affects 1 product.


Products: Ibm Lotus Connections.

## How do I fix CVE-2010-2279?

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

## Is CVE-2010-2279 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-4809](https://insights.sbomify.com/CVE-2008-4809/): Multiple unspecified vulnerabilities in the Profiles search pages in IBM Lotus Connections 2.x before 2.0.1 have unknown impact and attack v (critical 10.0)
- [CVE-2008-4806](https://insights.sbomify.com/CVE-2008-4806/): SQL injection in n/a (high 7.5)
- [CVE-2011-1032](https://insights.sbomify.com/CVE-2011-1032/): Missing authorization in n/a (medium 6.8)
- [CVE-2008-4808](https://insights.sbomify.com/CVE-2008-4808/): Information disclosure in n/a (medium 5.0)
- [CVE-2013-0503](https://insights.sbomify.com/CVE-2013-0503/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2279 and fix it if it is affected.

What it is: CVE-2010-2279 is a high-severity vulnerability in n/a, published on 14 Jun 2010. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2010-2279 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-2010-2279/ (Markdown: https://insights.sbomify.com/CVE-2010-2279/index.md)
```

## Sources

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

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