Openvpn Access ServerApplication · Openvpn
CVE-2020-15074
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenVPN 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenVPN Access Server versions older than 2.8.4 and version 2.9.5 generate new authentication tokens on client reconnect instead of reusing existing tokens. This allows attackers to bypass the original token expiry timestamp, potentially maintaining unauthorized access beyond the intended token lifetime.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openvpn Access ServerApplication
< 2.8.4>= 2.9.0, < 2.9.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if OpenVPN Access Server is installedRun 'dpkg -l | grep openvpn-as' (Debian/Ubuntu) or 'rpm -qa | grep openvpn-as' (RHEL/CentOS) to check for the OpenVPN Access Server package. Alternatively, check if the service 'openvpnas' is running via 'systemctl status openvpnas' or 'service openvpnas status'.Affected if The package or service is found, indicating OpenVPN Access Server is present.
-
Retrieve the installed version numberRun 'openvpn --version' or check the admin web interface by logging into https://<server-ip>/admin and viewing the 'System Status' page. The version is also visible in the output of 'dpkg -l openvpn-as' or 'rpm -qi openvpn-as'.Affected if A version number is returned from any of these methods.
-
Compare version against affected rangesCompare your installed version to the vulnerable ranges: versions older than 2.8.4 (any 2.8.x before 2.8.4), or versions 2.9.0 through 2.9.5. For example, 2.8.3 is affected, 2.8.4 is not; 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.9.4, and 2.9.5 are all affected.Affected if Your installed version falls into < 2.8.4 OR (>= 2.9.0 AND < 2.9.6).
You are affected if OpenVPN Access Server is installed and the running version is less than 2.8.4, or between 2.9.0 and 2.9.5 inclusive.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.8.42.9.6
Upgrade OpenVPN Access Server to version 2.8.4 or later, or version 2.9.6 or later to resolve the token reuse vulnerability.
Fix this in Openvpn Access Server
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-15074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-15074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data