What is CVE-2022-47522?A high-severity flaw in Ieee 802.11, explained.
CVE-2022-47522 is a high-severity flaw (CVSS 7.5) in Ieee 802.11, published on 15 April 2023. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.9%. If you run an affected version, plan in the vendor’s fix.
Published 15 April 2023. Record last updated 6 February 2025. We keep this page's data up to date.
What is CVE-2022-47522? In plain terms.
An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
The IEEE 802.11 specifications through 802.11ax allow physically proximate attackers to intercept (possibly cleartext) target-destined frames by spoofing a target's MAC address, sending Power Save frames to the access point, and then sending other frames to the access point (such as authentication frames or re-association frames) to remove the target's original security context. This behavior occurs because the specifications do not require an access point to purge its transmit queue before removing a client's pairwise encryption key.
What kind of flaw is it?
- CWE-290Authentication Bypass by Spoofing
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offHard: conditions must line up
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data, change data and take it offline
Severity vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Is CVE-2022-47522 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood fell
- Exploit likelihood jumped
CVE-2022-47522 scores 46. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2022-47522 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2022-47522? 59 products.
The published record lists 59 products from 2 vendors. If you run one of these, check your version, then go to the fix below.
- Application
Ieee 802.11
by Ieee
Affected versionsall versions - Hardware
Soho 250
by SonicWall
Affected versionsversion not specified - Operating system
Soho 250 Firmware
by SonicWall
Affected versionsversion not specified - Hardware
Soho 250w
by SonicWall
Affected versionsversion not specified - Operating system
Soho 250w Firmware
by SonicWall
Affected versionsversion not specified - Hardware
Sonicwave 224w
by SonicWall
Affected versionsversion not specified - Operating system
Sonicwave 224w Firmware
by SonicWall
Affected versionsversion not specified - Hardware
Sonicwave 231c
by SonicWall
Affected versionsversion not specified - Operating system
Sonicwave 231c Firmware
by SonicWall
Affected versionsversion not specified
How do I fix CVE-2022-47522? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2022-47522 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
The IEEE 802.11 specifications through 802.11ax allow physically proximate attackers to intercept (possibly cleartext) target-destined frames by spoofing a t...
- Matched to
- Ieee 802.11 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2022-47522 is a high-severity flaw in Ieee 802.11, published on 15 April 2023. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-47522 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.9%. That can change at any time, which is why we keep watching.
For Ieee 802.11: all versions. The record lists 59 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.