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

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • 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
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!