Bug #2958
open
OsmoSGSN doesn't authenticate on second/further ATTACH REQUEST
Added by laforge about 6 years ago.
Updated about 4 years ago.
Description
When a new/unknown MS performs an ATTACH REQUEST for the first time, it is authenticated.
However, if that same MS later performs a second ATTACH REQUEST, even with new P-TMSI/TLLI, it is not authenticated and we simply send an ATTACH ACCEPT. This is a security problem, as it means anyone can impersonate other known-existing IMSIs.
Files
- Assignee changed from 4368 to lynxis
- Status changed from New to In Progress
- Status changed from In Progress to Stalled
- % Done changed from 0 to 50
I've started to refactor the whole GMM Attach Request handling into one fsm.
This issue is already fixed in the new fsm implementation.
I've created the ttcn3 testcase
SGSN_Tests.TC_attach_second_attempt
for this.
- Related to Bug #3302: implement a FSM for GMM Attach Request added
The test is failing again, even under the new FSM.
The HLR integration into the test must be rewritten.
At the moment, the TTCN test case SGSN_Tests.TC_attach_second_attempt still fails, but this is fails, because the
second attach does not proceed, because TTCN explicit expect to see an Insert Subscriber Data Request.
This request will be never sent from the SGSN, because it has still valid key data.
- Status changed from Stalled to In Progress
- Priority changed from High to Normal
It's not only the SGSN Tests. The SGSN does not behave correctly. The sgsn_authentication have to be rewritten as well the integration of Auth Req/Response to fix the real problem.
- Status changed from In Progress to Stalled
- Assignee changed from lynxis to 4368
- Related to Bug #4221: create ttcn testcase for T3350 in combination with a PDP context added
Also available in: Atom
PDF