Prevent Invalid Curve Attack on 5G SUCI Feature #20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the UDM is utilizing a Go version that is earlier than 1.19, it may compute the shared secret using an uncompressed public key that is not validated. This absence of validation creates an opportunity for an attacker to exploit the vulnerability and calculate
the private key by sending arbitrary SUCIs to the UDM, which will then attempt to decrypt them using both its own private key and the attacker's public key. Therefore, reference to go 1.19, we check if the keys are operating on valid curve points before compute the shared secret.