# CVE-2011-0887: Auth bypass in n/a

> Remote attackers can hijack sessions on the SMC SMCD3G-CCR web portal by brute-forcing predictable time-based session IDs.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mq6m-4p32-2pqg

## What is CVE-2011-0887?

CVE-2011-0887 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web management portal on the SMC SMCD3G-CCR (aka Comcast Business Gateway) with firmware before 1.4.0.49.2 uses predictable session IDs based on time values, which makes it easier for remote attackers to hijack sessions via a brute-force attack on the userid cookie.

Weakness: CWE-310

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

It affects 2 products.


Products: Smc Networks Smcd3g-Ccr, Smc Networks Smcd3g-Ccr Firmware.

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

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

## Is CVE-2011-0887 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0887 exists.

Public exploit code:

- Comcast DOCSIS 3.0 Business Gateways - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-0885](https://insights.sbomify.com/CVE-2011-0885/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2011-0886](https://insights.sbomify.com/CVE-2011-0886/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0887 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Feb 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-0887 exists.

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-0887/ (Markdown: https://insights.sbomify.com/CVE-2011-0887/index.md)
```

## Sources

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

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