Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix/second ue release context without authentication #134

Closed

Conversation

donald1218
Copy link
Contributor

No description provided.

@@ -134,7 +134,8 @@ type AmfUe struct {
/* Pdu Sesseion context */
SmContextList sync.Map // map[int32]*SmContext, pdu session id as key
/* Related Context */
RanUe map[models.AccessType]*RanUe
RanUe map[models.AccessType]*RanUe
HoldingRanUe map[models.AccessType]*RanUe

Choose a reason for hiding this comment

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

  1. I think HoldingRanUe should support multiple RanUes per access type since more than 1 InitialUeMessage referring to the same AmfUe is possible.
  2. If a malicious UE sends InitialUeMessage without following actions, as my understanding to this PR, the original amfUe.ranUe will be replaced with this malicious UE and the genuine UE will be stored into HoldingRanUe. Will this cause any problem? (e.g. Can AmfUe still handle the request from the genuine UE?)

@donald1218 donald1218 closed this Jul 29, 2024
@donald1218 donald1218 deleted the fix/second-ue-releaseuecontext branch August 15, 2024 03:29
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.

2 participants