psa_asymmetric_verify accepts RSA signatures with trailing garbage #258
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto#258
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
psa_asymmetric_verifywith an RSA signature algorithm returns a success status not only if the provided signature is correct, but also if the provided signature consists of a correct signature followed by trailing junk.This is of limited concern since it does not allow forgery attacks: there's no way to leverage this into getting a message accepted if the private key holder didn't sign it. However it violates the expectation that RSA PKCS#1v1.5 signatures are unique (if S1 and S2 are two valid signatures of the same message then S1 is bitwise identical to S2), and the expectation that a valid RSA signature (whatever the padding method) has a given size.
Internal Jira reference: https://jira.arm.com/browse/IOTCRYPT-911