CVE-2021-23005

On all 7.x and 6.x versions (fixed in 8.0.0), when using a Quorum device for BIG-IQ high availability (HA) for automatic failover, BIG-IQ does not make use of…

published March 31, 2021

CVSS
—
EPSS
1%
Percentile
63.5
In the wild
Unconfirmed
What it is

⚠️ A missed handshake could leave your BIG-IQ device in a jam! When using a Quorum device for high availability, it’s not utilizing TLS with Corosync. That's like sending secret letters without sealing the envelope! 📬 Imagine if you were sending sensitive documents through the mail but forgot to lock them in a secure envelope. Anyone could open them up and read your top-secret plans! In this case, the lack of TLS means your data traffic between BIG-IQ and Corosync could be intercepted, just like those unsealed letters. An attacker could potentially eavesdrop on the communications between your BIG-IQ devices. This means sensitive information being exchanged could fall into the wrong hands, leading to unauthorized access or manipulation of critical configurations. While this doesn’t seem like a direct exploit yet, it’s certainly a chink in your armor!

Put simply

Imagine if you were sending sensitive documents through the mail but forgot to lock them in a secure envelope. Anyone could open them up and read your top-secret plans! In this case, the lack of TLS means your data traffic between BIG-IQ and Corosync could be intercepted, just like those unsealed letters. This vulnerability arises because BIG-IQ versions 6.x and 7.x do not implement TLS for the Corosync protocol in high availability scenarios. As a result, the data exchanged between devices lacks encryption, making it susceptible to interception and unauthorized access.

What to do

An attacker could potentially eavesdrop on the communications between your BIG-IQ devices. This means sensitive information being exchanged could fall into the wrong hands, leading to unauthorized access or manipulation of critical configurations. While this doesn’t seem like a direct exploit yet, it’s certainly a chink in your armor! To mitigate this risk, upgrade your BIG-IQ to version 8.0.0 or higher, where this issue is fixed. Additionally, ensure your network configuration uses TLS for secure communications. Continuous monitoring and auditing of configurations can also help catch any potential lapses in security. You've got this! By upgrading and securing your communications, you'll keep those sneaky eavesdroppers at bay. 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01034 · 63.5th percentile
Published
2021-03-31T17:41Z
EPSS history
Timeline
  • 31 MAR 17:41Z
    On all 7.x and 6.x versions (fixed in 8.0.0), when using a Quorum device for BIG-IQ high availability (HA) for automatic failover, BIG-IQ does not make use of…
    cvelistv5