# CVE-2024-32754: Johnson Controls Kantech KT1, KT2, and KT400 Door Controllers - Exposure of Sensitive Information

> Attackers can obtain sensitive device identifiers when the door controller is in factory reset mode, requiring initial setup configuration to mitigate.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jul 2024
- **Updated:** 27 Aug 2025
- **Also known as:** GHSA-5cpx-cp4v-x9v8

## What is CVE-2024-32754?

CVE-2024-32754 is a low-severity vulnerability in Johnson Controls Kantech KT1 Door Controller, Rev01, published on 4 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under certain circumstances, when the controller is in factory reset mode waiting for initial setup, it will broadcast its MAC address, serial number, and firmware version.  Once configured, the controller will no longer broadcast this information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-32754?


## How do I fix CVE-2024-32754?

No fix has been published for CVE-2024-32754 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-32754 being exploited?

There is no known exploitation of CVE-2024-32754 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32754 and fix it if it is affected.

What it is: CVE-2024-32754 is a low-severity vulnerability in Johnson Controls Kantech KT1 Door Controller, Rev01, published on 4 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32754 in the wild and no public exploit code.

Affected product: Johnson Controls Kantech KT1 Door Controller, Rev01. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32754/ (Markdown: https://insights.sbomify.com/CVE-2024-32754/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32754
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32754
- OSV: https://osv.dev/vulnerability/CVE-2024-32754

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32754/
Summaries are generated and may contain mistakes; the official description above is the record.