CVE-2020-13412
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 · uneditedAn issue was discovered in Aviatrix Controller before 5.4.1204. An API call on the web interface lacked a session token check to control access, leading to CSRF.
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 confidenceA Cross-Site Request Forgery (CSRF) vulnerability exists in Aviatrix Controller versions prior to 5.4.1204. The web interface API calls lack proper session token validation, allowing attackers to craft malicious requests that execute actions in the context of an authenticated user's session.
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.4.1204CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Controller installationLocate the Aviatrix Controller in your environment by checking for the service or its management web interface URL (typically on port 443). Confirm the system is your Aviatrix Controller and not another Aviatrix component.Affected if The Aviatrix Controller web interface is accessible and responds to requests.
-
Retrieve the Controller versionLog into the Aviatrix Controller web UI and navigate to the Settings > Maintenance > About section, or use the Aviatrix CLI command 'show version' on the Controller to obtain the installed software version number.Affected if You are able to retrieve a version number from the Controller.
-
Compare version against affected rangeCompare the retrieved version number to the affected range. Versions prior to 5.4.1204 (such as 5.4.x versions below 5.4.1204, or any 5.3.x, 5.2.x, etc.) are considered vulnerable. Versions 5.4.1204 and later are patched.Affected if The installed version is lower than 5.4.1204.
Your environment is affected if an Aviatrix Controller is running with a version number less than 5.4.1204, as these versions lack proper session token validation in their web interface API calls.
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 data5.4.1204
Upgrade Aviatrix Controller to version 5.4.1204 or later to obtain the session token validation fix. Alternatively, implement anti-CSRF tokens on affected API endpoints.
- Consultation3.0 h
- Implementation2.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13412 — 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-13412 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