# CVE-2006-0511: Auth bypass in n/a

> Failure to clear session data on idle timeout allows subsequent users to hijack sessions and gain unauthorized privileges in Blackboard Academic Suite.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xwp8-fr9p-xj9v

## What is CVE-2006-0511?

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

### Official description

Blackboard Academic Suite 6.0 and earlier does not properly clear session information when de-authenticating a user who is idle, which allows subsequent users to log in as the previous user and gain privileges.  NOTE: the vendor has disputed this issue, saying that "This is a customer specific issue related to their Kerberos authentication single sign-on application and not a vulnerability in the Blackboard product.

## Which versions are affected by CVE-2006-0511?

It affects 2 products.


Products: Blackboard Blackboard, Blackboard Blackboard Academic Suite.

## How do I fix CVE-2006-0511?

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

## Is CVE-2006-0511 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1007](https://insights.sbomify.com/CVE-2002-1007/): Cross-site scripting in n/a (high 7.5)
- [CVE-2004-1581](https://insights.sbomify.com/CVE-2004-1581/): Information disclosure in n/a (medium 5.0)
- [CVE-2006-4308](https://insights.sbomify.com/CVE-2006-4308/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-0511 and fix it if it is affected.

What it is: CVE-2006-0511 is a medium-severity authentication bypass vulnerability in n/a, published on 1 Feb 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-0511 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-2006-0511/ (Markdown: https://insights.sbomify.com/CVE-2006-0511/index.md)
```

## Sources

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

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