Credential cloning via firmware-embedded default keys
Published May 6, 2024 · Updated Aug 2, 2024
Insecure key storage in Integrated Control Technology tSec firmware allows attackers to clone MIFARE and DESFire credentials. The firmware binary embeds the factory-default ICT encryption keys, allowing recovery of the secrets needed to generate arbitrary site-code and card-number combinations. Exposure is limited to deployments using the default ICT encryption, where cloned credentials can impersonate legitimate cards at affected readers.
Summary
What happened
Insecure key storage in Integrated Control Technology tSec firmware allows attackers to clone MIFARE and DESFire credentials. The firmware binary embeds the factory-default ICT encryption keys, allowing recovery of the secrets needed to generate arbitrary site-code and card-number combinations. Exposure is limited to deployments using the default ICT encryption, where cloned credentials can impersonate legitimate cards at affected readers.
The record
- CVE
- CVE-2024-29941
- Published
- May 6, 2024
- Updated
- Aug 2, 2024
- Vendor
- Integrated Control Technology
- Product
- tSec
- Classifications
- CWE-522
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=*
- Affected versionversion=0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo