# CVE-2008-5082: Auth bypass in n/a

> Authenticated users with enrollment privileges can bypass hardware key authentication policies by using software keys during token enrollment.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j872-hj4c-mqf5

## What is CVE-2008-5082?

CVE-2008-5082 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The verifyProof function in the Token Processing System (TPS) component in Red Hat Certificate System (RHCS) 7.1 through 7.3 and Dogtag Certificate System 1.0 returns successfully even when token enrollment did not use the hardware key, which allows remote authenticated users with enrollment privileges to bypass intended authentication policies by performing enrollment with a software key.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2008-5082?

It affects 2 products.


Products: Redhat  Dogtag Certificate System, Redhat Certificate System.

## How do I fix CVE-2008-5082?

Apply the vendor's patch.

## Is CVE-2008-5082 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5082 and fix it if it is affected.

What it is: CVE-2008-5082 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-5082 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-2008-5082/ (Markdown: https://insights.sbomify.com/CVE-2008-5082/index.md)
```

## Sources

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

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