The vulnerability that killed FreeWifi_Secure #1462
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.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
What broke and why
Free’s carrier Wi‑Fi SSID
FreeWifi_secure
(also seen asFreeWifi_Secure
) authenticated Free Mobile subscribers using EAP‑SIM (RFC 4186) over 802.1X. During the unauthenticated identity phase, client devices replied toEAP-Request/Identity
with a permanent identifier in cleartext: the subscriber’s IMSI encoded as a 3GPP NAI, e.g.,20815XXXXXXXXXX@wlan.mnc015.mcc208.3gppnetwork.org
. No protected identity (3...🔧 Technical Details
Passive IMSI harvesting on EAP‑SIM networks lacking identity privacy: On SIM‑based Wi‑Fi where
EAP-Response/Identity
carries the permanent IMSI, capture the first EAP identity exchange and read the NAI (e.g.,20815XXXXXXXXXX@wlan.mnc015.mcc208.3gppnetwork.org
). Steps: enable monitor mode (airmon-ng start <iface>
), capture with Wireshark/Kismet/tcpdump, and filter for identity frames (eap.code == 2 && eap.type == 1
). The leak occurs before any TLS tunnel, so the IMSI appears as ASCII. This generalizes to any EAP‑SIM/AKA deployment that omits pseudonyms or tunneling.Abusing the identifier downstream: Use the captured IMSI for cross‑site device correlation and, where access exists, SS7/Diameter lookups for location, call/SMS interception, and MFA theft. The Wi‑Fi capture is only the bootstrap; the real power comes from telecom signaling abuse once the IMSI is known.
🤖 Agent Actions
I explored the repository structure, reviewed relevant content, and implemented an update to cover the EAP-SIM/EAP-AKA IMSI exposure technique described in the blog.
What I checked (at least 5 files):
Rationale for placement:
Changes made:
Tool actions performed:
Why this is useful:
No new files were created; the update fits well into the existing Wi‑Fi methodology page and maintains HackTricks structure and style.
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.
📚 Repository Maintenance
All .md files have been checked for proper formatting (headers, includes, etc.).