CommitWatch RSS
AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Moderate 59 Bitcoin

feat(core): Update RFAL library to version 4.0.2

TZ151ff869 View source ↗
Public commit record

What the developer wrote

Authored by kopecdav

57/100 · Thin
feat(core): Update RFAL library to version 4.0.2

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit updates the third-party STMicroelectronics RFAL NFC library inside Trezor firmware from version 3.0.1 to 4.0.2. The vendor's release notes for version 4.0.2 explicitly mention fixing a 'vulnerability during EMD handling on fast systems' that was introduced in version 4.0.0. EMD (Electro-Magnetic Disturbance) handling is part of the NFC radio stack, so the flaw is likely a low-level radio/communication issue rather than something that directly exposes cryptocurrency private keys. Because the commit is a large library drop (almost 8,000 lines changed across 55 files) and the actual code diff is not shown, we cannot independently verify the exact nature or severity of the vulnerability from this commit alone.

Recommended action

Treat this as a routine but security-relevant dependency update. Review the RFAL v4.0.2 upstream release notes and, if available, the upstream commit or diff for the EMD-handling fix. Run NFC regression and fuzz/EMD tests before shipping firmware that includes this update. Consider adding a changelog entry because the upstream release explicitly calls the fix a vulnerability.

Security signals we found

01

Vendor release notes label v4.0.2 change as 'Fixed vulnerability during EMD handling on fast systems'

02

Large third-party library version bump (3.0.1 -> 4.0.2) with many source files changed

03

No independent diff of the vulnerability fix is supplied in the commit excerpt

04

No CVE, advisory, or changelog entry in the commit message

Risk score

Why this scored 59/100

Our methodology →
Potential impact 18/30
Exploitability 12/25
Stealth signal 10/15
Affected reach 10/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.

More from Trezor firmware

Related watches

Low 27 AI analysisMessage 93 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): digest EIP-1559/EIP-7702 magic without RLP encoding

This commit is a small internal cleanup in Trezor's Ethereum signing code. It changes how two special 'magic' bytes (the transaction type markers for newer Ethereum transaction formats) are fed into the cryptographic hash. Previously the c…

Refactor of cryptographic hashing path for Ethereum transaction signingRemoval of implicit assumption that RLP encodes small integers as single bytesChange affects EIP-1559 and EIP-7702 transaction type markers
2362bc6fby Roman Zeyde+6−32 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 98 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): test RLP self-encoding bytestrings

This commit only adds a new unit test to the Trezor firmware codebase. It verifies that very short Ethereum RLP-encoded byte strings and small positive integers encode to themselves, which is a known property of the RLP specification. No p…

41538733by Roman Zeyde+16−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove sha1 from regular FW

This commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…

Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
16d15774by M1nd3r+0−2006 files
No security note in commit
Open full analysis →Source commit ↗