CVE-2020-27568
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 · uneditedInsecure File Permissions exist in Aviatrix Controller 5.3.1516. Several world writable files and directories were found in the controller resource. Note: All Aviatrix appliances are fully encrypted. This is an extra layer of security.
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 · moderate confidenceInsecure file permissions vulnerability in Aviatrix Controller 5.3.1516 allows world-writable access to several files and directories on the controller system. This misconfiguration enables any local user to modify these files, potentially leading to privilege escalation or arbitrary code execution.
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= 5.3.1516CVSS 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.
-
Confirm Aviatrix Controller is installedLocate the Aviatrix Controller installation directory or check for running processes related to Aviatrix (e.g., ps aux | grep -i aviatrix)Affected if Aviatrix Controller software is present on the system
-
Identify installed versionRun command to retrieve Aviatrix Controller version (e.g., avxctl --version, or check /opt/aviatrix version file, or inspect controller UI for version info)Affected if Version reported is 5.3.1516
-
Locate installation directoriesFind the primary Aviatrix installation path (common locations include /opt/aviatrix, /home/aviatrix, or /usr/local/aviatrix)Affected if Installation directory exists on the system
-
Scan for world-writable files and directoriesRun: find <aviatrix_install_path> -perm -002 -type f (for files) and find <aviatrix_install_path> -perm -002 -type d (for directories) to list all world-writable itemsAffected if Any files or directories under the Aviatrix installation have world-writable (o+w) permissions set
-
Verify world-writable items in system directoriesCheck /var/lib/aviatrix, /var/log/aviatrix, /etc/aviatrix for world-writable permissions using ls -laAffected if Configuration, data, or log directories used by Aviatrix are world-writable
The environment is affected if Aviatrix Controller version 5.3.1516 is running AND world-writable files or directories exist within the Aviatrix installation or data directories.
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 dataRestrict file permissions on the affected files and directories by removing world-writable access and setting appropriate owner/group permissions (e.g., 644 for files, 755 for directories).
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27568 — 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-27568 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