Skip to content

nuttx/drivers/crypto/pnt/pnt_se05x_api: Minor Overflow in Secure Element#19230

Open
catalinv-ncc wants to merge 1 commit into
apache:masterfrom
catalinv-ncc:bug/Minor_Overflow_in_SE_Driver_May_Cause_DoS
Open

nuttx/drivers/crypto/pnt/pnt_se05x_api: Minor Overflow in Secure Element#19230
catalinv-ncc wants to merge 1 commit into
apache:masterfrom
catalinv-ncc:bug/Minor_Overflow_in_SE_Driver_May_Cause_DoS

Conversation

@catalinv-ncc

Copy link
Copy Markdown
Contributor

Driver May Cause a DoS

Invalid data is passed to the NXP Plug & Trust Nano Package used
by the NuttX secure element driver. If the NXP code is not handling
the malformed data, a corruption can occur. Alternatively, if the
attacker is able to point create_signature_args->algorithm in
memory at an address that is not accessible, a crash can occur.

Applicable to:

  • signature_algorithm_mapping[create_signature_args->algorithm]
  • signature_algorithm_mapping[verify_signature_args->algorithm]

Tested locally, builds fine.

Driver May Cause a DoS

Invalid data is passed to the NXP Plug & Trust Nano Package used by the
NuttX secure element driver. If the NXP code is not handling the malformed
data, a corruption can occur. Alternatively, if the attacker is able to
point create_signature_args->algorithm in memory at an address that is not
accessible, a crash can occur.

Applicable to:
* `signature_algorithm_mapping[create_signature_args->algorithm]`
* `signature_algorithm_mapping[verify_signature_args->algorithm]`

Signed-off-by: Catalin Visinescu <catalin_visinescu@yahoo.com>
@catalinv-ncc catalinv-ncc requested a review from jerpelea as a code owner June 27, 2026 19:53
@github-actions github-actions Bot added Size: S The size of the change in this PR is small Area: Crypto labels Jun 27, 2026
@github-actions

Copy link
Copy Markdown

MemBrowse Memory Report

No memory changes detected for:

@catalinv-ncc

Copy link
Copy Markdown
Contributor Author

I have observed the coding style errors, but these are not related to the changes I've made. The lines where I modified the code are not listed as problematic. Not sure what is the process for this.

Please advise, thanks.

@acassis

acassis commented Jun 27, 2026

Copy link
Copy Markdown
Contributor

@catalinv-ncc I think those style error are from original crypto API, you don't need to fix them. They were kept to way to simplify the compatibility.

If you prefer you can create a separated PR adding these symbols to g_white_content_list[] this way this PR will pass without these CI errors.

@linguini1

Copy link
Copy Markdown
Contributor

Can you please follow the PR template?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: Crypto Size: S The size of the change in this PR is small

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants