CVE-2024-29206

An Improper Access Control could allow a malicious actor authenticated in the API to enable Android Debug Bridge (ADB) and make unsupported changes to the system.

Affected Products:

UniFi Connect EV Station (Version 1.1.18 and earlier)

UniFi Connect EV Station Pro (Version 1.1.18 and earlier)

UniFi Access G2 Reader Pro (Version 1.2.172 and earlier)

UniFi Access Reader Pro (Version 2.7.238 and earlier)

UniFi Access Intercom (Version 1.0.66 and earlier)

UniFi Access Intercom Viewer (Version 1.0.5 and earlier)

UniFi Connect Display (Version 1.9.324 and earlier)

UniFi Connect Display Cast (Version 1.6.225 and earlier)

Mitigation:

Update UniFi Connect Application to Version 3.10.7 or later.

Update UniFi Connect EV Station to Version 1.2.15 or later.

Update UniFi Connect EV Station Pro to Version 1.2.15 or later.

Update UniFi Access G2 Reader Pro Version 1.3.37 or later.

Update UniFi Access Reader Pro Version 2.8.19 or later.

Update UniFi Access Intercom Version 1.1.32 or later.

Update UniFi Access Intercom Viewer Version 1.1.6 or later.

Update UniFi Connect Display to Version 1.11.348 or later.

Update UniFi Connect Display Cast to Version 1.8.255 or later.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/19.html
• https://cwe.mitre.org/data/definitions/441.html
• https://cwe.mitre.org/data/definitions/478.html
• https://cwe.mitre.org/data/definitions/479.html
• https://cwe.mitre.org/data/definitions/502.html
• https://cwe.mitre.org/data/definitions/503.html
• https://cwe.mitre.org/data/definitions/536.html
• https://cwe.mitre.org/data/definitions/546.html
• https://cwe.mitre.org/data/definitions/550.html
• https://cwe.mitre.org/data/definitions/551.html
• https://cwe.mitre.org/data/definitions/552.html
• https://cwe.mitre.org/data/definitions/556.html
• https://cwe.mitre.org/data/definitions/558.html
• https://cwe.mitre.org/data/definitions/562.html
• https://cwe.mitre.org/data/definitions/563.html
• https://cwe.mitre.org/data/definitions/564.html
• https://cwe.mitre.org/data/definitions/578.html

References

• https://community.ui.com/releases/Security-Advisory-bulletin-039-039/44e24007-2c2c-4ac0-bebf-3f19b9b24f09