Time-Stamp Protocol (RFC 3161)#10778
Conversation
76af38a to
dc97de1
Compare
|
2a0657a to
0d3affa
Compare
|
Jenkins: retest this please |
wolfSSL-Fenrir-bot
left a comment
There was a problem hiding this comment.
Fenrir Automated Review — PR #10778
Scan targets checked: wolfcrypt-bugs, wolfcrypt-port-bugs, wolfcrypt-rs-bugs, wolfcrypt-src, wolfssl-bugs, wolfssl-src
Findings: 2
1 finding(s) posted as inline comments (see file-level comments below)
Low (1)
asn_orig.c DecodeExtKeyUsage skips counting unrecognized OIDs
File: wolfcrypt/src/asn_orig.c:3959
Function: DecodeExtKeyUsage
Category: Copy-paste errors
The original-parser DecodeExtKeyUsage does continue on ASN_UNKNOWN_OID_E, bypassing the extExtKeyUsageOidCnt increment, so unknown KeyPurposeIds are not counted — contradicting its own comment and diverging from the template version in asn.c which does count them. A cert with timeStamping plus an extra unknown EKU would report count 1 and wrongly pass Tsp_CheckSignerCert's extExtKeyUsageOidCnt != 1 gate.
Recommendation: Count the OID before continue (or increment in the unknown-OID branch) so the original parser matches the template version's count semantics.
Referenced code: wolfcrypt/src/asn_orig.c:3959-3965 (7 lines)
This review was generated automatically by Fenrir. Findings are non-blocking.
Implementation in wolfCrypt OpenSSL compatibility layer in wolfSSL Added tests, certificates, examples.
0d3affa to
0b151dc
Compare
|
DecodeExtKeyUsage fixed |
Description
Implementation in wolfCrypt
OpenSSL compatibility layer in wolfSSL
Added tests, certificates, examples.
Testing
Different configuration with --enable-tsp.