# CVE-2010-2977: Weak cryptography in n/a

> Improper TLS/SSL implementation in Cisco UWN allows remote attackers to bypass security controls.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 9 Aug 2010
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-8j3h-fw74-536v

## What is CVE-2010-2977?

CVE-2010-2977 is a critical vulnerability in n/a, published on 9 Aug 2010. It can be exploited over the network.

### Official description

Cisco Unified Wireless Network (UWN) Solution 7.x before 7.0.98.0 does not properly implement TLS and SSL, which has unspecified impact and remote attack vectors, aka Bug ID CSCtd01611.

Weakness: CWE-16

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

It affects 1 product.


Products: Cisco Unified Wireless Network Solution Software.

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

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

## Is CVE-2010-2977 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-2976](https://insights.sbomify.com/CVE-2010-2976/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2010-2978](https://insights.sbomify.com/CVE-2010-2978/): Weak cryptography in n/a (critical 10.0)
- [CVE-2010-2984](https://insights.sbomify.com/CVE-2010-2984/): Auth bypass in n/a (critical 10.0)
- [CVE-2010-2979](https://insights.sbomify.com/CVE-2010-2979/): Denial of service in n/a (high 7.8)
- [CVE-2010-2980](https://insights.sbomify.com/CVE-2010-2980/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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