Skip to content
Fencer Vulns
high 7.5

CVE-2023-0248 json

Kantech Gen1 ioSmart card reader

published 2023-12-14 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-12329

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

Summary

An attacker with physical access to the Kantech Gen1 ioSmart card reader with firmware version prior to 1.07.02 in certain circumstances can recover the reader's communication memory between the card and reader.

Patch / fix

  • Sensormatic Electronics, a subsidiary of Johnson Controls, Inc. ioSmart Gen1 1.07.02

Vendor advisories

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

cisa ICSA-23-348-02 updated cvss 7.5

Johnson Controls Kantech Gen1 ioSmart

  • Sensormatic Electronics, LLC, an affiliate of Johnson Controls Inc. Kantech Gen1 ioSmart card reader firmware <1.7.2
    affected: vendor fix, mitigation “Johnson Controls also makes the following recommendations and wishes to provide the following information:” kantech.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.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected products

  • Sensormatic Electronics, a subsidiary of Johnson Controls, Inc. ioSmart Gen1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-401 Missing Release of Memory after Effective Lifetime

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.