Skip to content
Fencer Vulns
low 3.1

CVE-2024-32754 json

Johnson Controls Kantech KT1, KT2, and KT400 Door Controllers - Exposure of Sensitive Information

published 2024-07-04 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-30541

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-24-184-01 updated cvss 3.1

Johnson Controls Kantech Door Controllers

  • Johnson Controls, Inc. Kantech KT1 Door Controller, Rev01 <=2.09.01 Johnson Controls, Inc. Kantech KT2 Door Controller, Rev01 <=2.09.01 Johnson Controls, Inc. Kantech KT400 Door Controller, Rev01 <=3.01.16
    affected: mitigation “Johnson Controls recommends users update Kantech door controllers as follows:” johnsoncontrols.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Johnson Controls Kantech KT1 Door Controller, Rev01
  • Johnson Controls Kantech KT2 Door Controller, Rev01
  • Johnson Controls Kantech KT400 Door Controller, Rev01

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.