Skip to content

wolfCrypt API hardening: input validation, key zeroization, hardware ports#10468

Merged
SparkiDev merged 3 commits into
wolfSSL:masterfrom
JeremiahM37:fenrir-wolfcrypt-api-hardening
May 14, 2026
Merged

wolfCrypt API hardening: input validation, key zeroization, hardware ports#10468
SparkiDev merged 3 commits into
wolfSSL:masterfrom
JeremiahM37:fenrir-wolfcrypt-api-hardening

Conversation

@JeremiahM37

Copy link
Copy Markdown
Contributor

Fixes F-2214, F-3751, F-3752, F-3753, F-3754, F-3773, F-3782

  • curve25519: reject NULL rng in wc_curve25519_make_pub_blind / generic_blind
  • wolfentropy: reject NULL output and non-positive size in wc_Entropy_Get / GetRawEntropy
  • rc2: add wc_Rc2Free to zero key schedule via ForceZero (plus test)
  • TSIP RSA: initialize ret to CRYPTOCB_UNAVAILABLE on unsupported key / failed import
  • casper RSA: bound exponent write to 4 bytes and assemble uint32_t portably

@JeremiahM37 JeremiahM37 self-assigned this May 12, 2026
@JeremiahM37
JeremiahM37 force-pushed the fenrir-wolfcrypt-api-hardening branch from f9839b5 to 7b2625c Compare May 12, 2026 19:40
@JeremiahM37
JeremiahM37 force-pushed the fenrir-wolfcrypt-api-hardening branch from 7b2625c to b235af7 Compare May 12, 2026 20:58
@JeremiahM37

Copy link
Copy Markdown
Contributor Author

Jenkins retest this please

@github-actions

Copy link
Copy Markdown

MemBrowse Memory Report

No memory changes detected for:

@wolfSSL-Fenrir-bot wolfSSL-Fenrir-bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fenrir Automated Review — PR #10468

Scan targets checked: wolfcrypt-bugs, wolfcrypt-port-bugs, wolfcrypt-src

No new issues found in the changed files. ✅

@SparkiDev
SparkiDev merged commit 31a76d3 into wolfSSL:master May 14, 2026
469 of 525 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants