OpenvpnApplication · Aviatrix
CVE-2020-27569
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 · uneditedArbitrary File Write exists in Aviatrix VPN Client 2.8.2 and earlier. The VPN service writes logs to a location that is world writable and can be leveraged to gain write access to any file on the system.
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 confidenceThe Aviatrix VPN Client versions 2.8.2 and earlier writes log files to a world-writable location, allowing any local user to modify these log files. This arbitrary file write capability can be exploited to overwrite system files or escalate privileges by writing to sensitive locations.
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
OpenvpnApplication
<= 2.8.2CVSS 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 Aviatrix VPN Client installationRun 'avxadmin --version' or check the installed packages via system package manager (dpkg -l, rpm -qa) for Aviatrix OpenVPN or Aviatrix VPN ClientAffected if The installed version is 2.8.2 or earlier
-
Locate log files created by Aviatrix VPN ClientCheck common log directories such as /var/log/, /tmp/, or the user's home directory for files with names containing 'aviatrix', 'avx', 'vpn', or 'openvpn'Affected if Log files exist in a world-writable location such as /tmp/ or a world-writable directory
-
Verify log file permissionsRun 'ls -la' on the identified log files and check the permission bits - look for 'w' permission for 'others' (e.g., -rw-rw-rw-)Affected if Log files have world-writable permissions (mode 666 or similar)
-
Check log directory permissionsRun 'ls -ld' on the directory containing Aviatrix VPN logs and verify if the directory allows write access to all usersAffected if The parent directory of log files is world-writable (e.g., drwxrwxrwx)
A system is affected if the Aviatrix VPN Client version is 2.8.2 or earlier AND log files are stored in a world-writable location accessible to unprivileged local users.
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 dataUpgrade the Aviatrix VPN Client to a version newer than 2.8.2 that fixes the world-writable log file issue, or implement file permission controls to restrict write access to the log directory.
Fix this in Openvpn
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27569 — 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-27569 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