dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-29207

HIGH · 7.5 CVSS v3.0 Published 2024-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
No privileges Zero-click

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 · unedited
An Improper Certificate Validation could allow a malicious actor with access to an adjacent network to take control of the system. Affected Products: UniFi Connect Application (Version 3.7.9 and earlier) UniFi Connect EV Station (Version 1.1.18 and earlier) UniFi Connect EV Station Pro (Version 1.1.18 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 Connect Display to Version 1.11.348 or later. Update UniFi Connect Display Cast to Version 1.8.255 or later.

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 confidence

Improper certificate validation in UniFi Connect applications allows a man-in-the-middle attack from an adjacent network, potentially giving attackers control of the system by intercepting or spoofing network communications.

MitigationUpdate all affected UniFi Connect products to their patched versions to remediate the certificate validation vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:H/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify UniFi Connect installation
    Check for UniFi Connect applications on the system. Look for process names containing 'unifi', 'connect', or related services. On Linux, check /var/lib/unifi or similar directories. On Windows, check Program Files for UniFi Connect components.
    Affected if UniFi Connect applications are installed and running on the system
  2. Determine installed UniFi Connect version
    Locate the version information for the installed UniFi Connect software. Check application metadata, log files, or use command-line tools like 'dpkg -l' (Linux), 'choco list' (Windows), or the application's built-in version check if available.
    Affected if The installed version cannot be determined or is earlier than the patched release
  3. Compare version to affected range
    Compare your installed version against the known affected version range for this CVE. Since specific version ranges were not provided in the CVE advisory, treat any unpatched UniFi Connect installation as potentially affected.
    Affected if The installed version falls within or cannot be confirmed as outside the vulnerable version range
  4. Verify network exposure
    Check if the UniFi Connect application is configured to accept network connections. This vulnerability allows MITM attacks from an adjacent network, so inspect network binding configurations and firewall rules.
    Affected if UniFi Connect is listening on network interfaces accessible to adjacent networks

The system is affected if UniFi Connect is installed with a version that has not been patched for the certificate validation vulnerability, and the application handles network communications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all affected UniFi Connect products to their patched versions to remediate the certificate validation vulnerability.

Recommended fix High confidence

UniFi Connect Application >=3.10.7; UniFi Connect EV Station >=1.2.15; UniFi Connect EV Station Pro >=1.2.15; UniFi Connect Display >=1.11.348; UniFi Connect Display Cast >=1.8.255

  1. Identify which UniFi Connect product(s) are deployed in your environment (Application, EV Station, EV Station Pro, Display, or Display Cast)
  2. Determine the current installed version of each UniFi Connect product
  3. For UniFi Connect Application: Upgrade to version 3.10.7 or later
  4. For UniFi Connect EV Station: Upgrade to version 1.2.15 or later
  5. For UniFi Connect EV Station Pro: Upgrade to version 1.2.15 or later
  6. For UniFi Connect Display: Upgrade to version 1.11.348 or later
  7. For UniFi Connect Display Cast: Upgrade to version 1.8.255 or later
  8. After upgrading, verify the new version is installed and the service is running properly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29207 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29207 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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