dbcve.org
CWE-924Weakness · CWE-924

CVE-2025-29628

CRITICAL · 9.4 CVSS v3.1 Published 2025-07-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
A Gardyn Azure IoT Hub connection string is downloaded over an insecure HTTP connection in Gardyn Home Kit firmware before master.619, Home Kit Mobile Application before 2.11.0, and Home Kit Cloud API before 2.12.2026 leaving the string vulnerable to interception and modification through a Man-in-the-Middle attack. This may result in the attacker capturing device credentials or taking control of vulnerable home kits.

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 confidence

Gardyn Azure IoT Hub connection strings are downloaded over unencrypted HTTP, allowing Man-in-the-Middle attackers positioned on the network path to intercept and modify these credentials, potentially capturing device credentials or gaining full control of vulnerable home kits.

MitigationImplement HTTPS with proper certificate validation for all connection string downloads across firmware, mobile application, and cloud API components. Ensure all three affected components (firmware, mobile app, cloud API) are updated to patched versions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L

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 Gardyn Home Kit presence
    Inventory your network and IoT devices to confirm you have any Gardyn Home Kit products deployed, including the Gardyn tower unit and associated mobile app
    Affected if A Gardyn Home Kit device is present in the environment
  2. Check Gardyn device firmware version
    Access the Gardyn device settings through the mobile app or device interface and locate the firmware version information, typically found under Settings > Device Info or About
    Affected if Firmware version is master.618 or earlier (below the patched version master.619)
  3. Check mobile app version
    Open your mobile app store (Google Play or Apple App Store), find the Gardyn app, and check the installed version under your device app settings or the store listing
    Affected if Mobile app version is 2.10.x or earlier (below patched version 2.11.0)
  4. Inspect network traffic for HTTP Azure connections
    Use a network sniffer or proxy on the same network segment as the Gardyn device to capture traffic. Filter for HTTP (port 80) connections to Azure IoT Hub endpoints or any outgoing HTTP connections from the Gardyn device
    Affected if The device or app initiates unencrypted HTTP connections to Azure IoT Hub or Gardyn cloud servers instead of HTTPS
  5. Verify connection string retrieval method
    If possible, inspect network logs or use packet capture during device setup/app initialization to observe how connection strings are downloaded. Look for HTTP requests without TLS encryption
    Affected if Connection strings are fetched over HTTP instead of HTTPS

You are affected if you have a Gardyn Home Kit with firmware below master.619, mobile app below 2.11.0, or you observe unencrypted HTTP traffic from the device to Azure IoT Hub during connection string download.

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

Implement HTTPS with proper certificate validation for all connection string downloads across firmware, mobile application, and cloud API components. Ensure all three affected components (firmware, mobile app, cloud API) are updated to patched versions.

Recommended fix High confidence

Firmware: master.619 or later; Mobile App: 2.11.0 or later; Cloud API: 2.12.2026 or later

  1. Identify all Gardyn Home Kit components in your deployment (firmware devices, mobile applications, and cloud API instances)
  2. Upgrade Gardyn Home Kit firmware on all devices to version master.619 or later
  3. Upgrade Home Kit Mobile Application to version 2.11.0 or later (available in app stores)
  4. Upgrade Home Kit Cloud API to version 2.12.2026 or later
  5. Verify that Azure IoT Hub connection strings are now retrieved over HTTPS instead of HTTP

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-29628 — 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-2025-29628 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