Recommended Posts

WIRED EQUIVALENT PRIVACY (WEP) a wireless security measure

hi, I need to try and find more information on WEP I am doing a project (1 of many ) and i need to learn everything I can about WEP ... in extreme detail .. I need to see how and why it is so easily exploited with detailed explanations (I dont need to know how to hack it...just making that clear)

any help will be great..

once again to be clear (just so admins know) I am not asking how to hack a WEP I am asking about the wifi encryption standard and details on the know exploits .. for example, when a key is being obtained handshakes and arps are exchanged ... why? how? what is then done with the information? etc

Link to comment
https://www.neowin.net/forum/topic/1139420-i-need-information-on-wep/
Share on other sites

Join a college/university that subscribes and you'll get it free.

I will get it from my uni then they should have it

You don't learn (and actually understand) that stuff in "extreme" detail in a short amount of time. It's like saying you want to know physical chemistry but don't want to get bogged down with all those orbital shapes and baryons and stuff. To get a solid understanding is going to take some real work so maybe you want to scale back a bit.

I Know I say in my post I need to know everything ... its more... I need access to everything but I know specifically what I am looking for :p its just to long to google search it and I was just coming here for sources or someone with an expert knowledge... I have read your post and will take your points on .... I am going to start ... there is a couple of issues with wep that I will be directly addressing for a program I am writing ... simple OPN WEP to start with then eventually moving on untill my program has all aspects of WEP security down..

Have a listen. This is from Security Now #89

Even More Badly Broken WEP

Leo and I review the operation of wireless network security and discuss in detail the operation of the latest attack on the increasingly insecure WEP encryption system. This new technique allows any WEP-protected WiFi network's secret cryptographic key to be discovered in less than 60 seconds.

http://www.grc.com/sn/past/2007.htm

http://media.grc.com/sn/sn-089.mp3

Kinda the opposite of RTFM: the FM tells you how it's supposed to work and how to build an implementation. It doesn't tell you why an implementation is weak (if it did, we'd never have used it). I went for more of a "read the bug reports and patch notes" recommendation.

[/color]

It sounds more like you don't really care about how or why WEP is weak - that's going to be a discussion for math or comp-sci nerds who like to use lots of letters and symbols when they talk about things. You sound like you're more interested in the steps necessary to exploit a vulnerability.

Consider two imaginary descriptions of a weakness in some piece of cryptographic software:

  • Algorithm X has a bias in byte 3 that makes it 1/2^384 % more likely to return 0 than any other a-bit sequence. You can use that to discover 1 bit of key information in time 2^56 with 95% probability. (1.5 assloads of math and stats follow here. Lots of brackets and letters)
  • Capture 300,000 packets, then compute byte 5 + byte 9 xor byte 3 for each packet. Count how many times you get 1, 2,3,4,5,? as a result of that calculation and store the the number of times for each value. If a value occurs twice as often as any other number then there is a 95% chance that bit 4 of that value is bit #7 in the key. if you get { 1= 953, 2=888, 3=1,965, 3=1,001, 4=920? } then there's a good chance that the 7th bit in the key is 0 (because 3 occurs most often, 3dec = 0b0000011, so bit #4 is 0, so bit #7 of the key is probably 0). You can use this new information about the key + new packets + different calculations to determine the value of more bits in the key.

The first answer is what you'll get out of comp-sci text books and papers. It's the "real understanding" of why WEP is weak. You will see bits of the second in research papers but its typically a mathematical description rather than an algorithm. If you're not a huge math nerd it's going to be somewhat difficult to convert that into a useful algorithm. On the plus side, you know why those algorithms work.

If you prefer the second kind of answer then you're probably best off just reading the source code for a tool like aircrack-ng or metasploit. It won't give you an understanding about why the code works, but you will understand how to use it. The second is saying "you can perform a statistical attack" but it hand-waves passed the details about why particular data is used or exactly how it reveals particular bits of key information (why byte 5+9 and not 7+6? why do we get the bit in the key at postion 7 instead of 3? why do we need 300k packets and not 3m or 300?). If you don't really care why it works then reading the source code is the quickest way to enlightenment.

you are half right :p while I am looking as to how its exploited (i am not looking to exploit it with a program like aircrack and aireplay I want to know what these programs do to exploit it) but I feel I should have an understanding of the math as well but not to a massive indepth level to the point that I can write a book my self :p

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!