Skip to main content
VulnerabilityPublished

CVE-2025-2171: Aviatrix Controller · Improper Restriction of Excessive Authentication Attempts

Affects Aviatrix ControllerSource CVE Database V5

0

Public exploit available · CVSS 7.8 High · fixed in 8.0.0 : patch Aviatrix Controller as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 8.0.0, 7.2.5090, 7.1.4208
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Aviatrix Controller to 8.0.0, 7.2.5090 or 7.1.4208.

Affected software

ProductAffectedFixed in
Aviatrix ControllerAffected
  • <7.1.4208
  • <7.2.5090
  • <8.0.0
Fixed in
  • 7.1.4208
  • 7.2.5090
  • 8.0.0

AI-suggested

  1. Immediate patching: Organizations should upgrade Aviatrix Controller to versions 7.1.4208, 7.2.5090, 8.0.0 or later, where this vulnerability is addressed.
  2. Implement compensating controls: Until patches are applied, restrict network access to the Aviatrix Controller management interface using IP whitelisting, VPNs, or firewall rules to limit exposure to trusted administrators only.
  3. Monitor and alert: Deploy monitoring to detect abnormal password reset attempts or repeated failed authentication attempts targeting the password reset PIN.
  4. Enforce multi-factor authentication (MFA): Where possible, enable MFA on the Aviatrix Controller to add an additional layer of security beyond the PIN.
  5. Review and harden password reset policies: Work with Aviatrix support or administrators to implement custom rate limiting or lockout mechanisms if supported.
  6. Conduct regular audits: Verify that no unauthorized password resets or configuration changes have occurred.
  7. Network segmentation: Isolate the Aviatrix Controller management network segment from general user networks to reduce attack surface. These steps go beyond generic advice by focusing on immediate patching combined with network access restrictions and active monitoring tailored to the specific vulnerability vector.

Description

Aviatrix Controller versions prior to 7.1.4208, 7.2.5090, and 8.0.0 do not enforce rate limiting on password reset attempts, allowing adversaries to brute force guess the 6-digit password reset PIN

References

Community reviews

Loading reviews…