Improper input validation in firmware for some Intel(R) PROSet/Wireless WiFi in UEFI may allow an unauthenticated user to potentially enable
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: kernel-firmware (openSUSE:Leap 15.3) 20210208-150300.4.7.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 20200107-150100.3.31.1; kernel-firmware (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 20210208-150300.4.7.1.
Low priority for now. Upgrade to kernel-firmware (openSUSE:Leap 15.3) 20210208-150300.4.7.1; kernel-firmware (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 20200107-150100.3.31.1; kernel-firmware (SUSE:Linux Enterprise Module for Basesystem 15 SP3) 20210208-150300.4.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Improper input validation in firmware for some Intel(R) PROSet/Wireless WiFi in UEFI may allow an unauthenticated user to potentially enable escalation of privilege via adjacent access.
- Published
- Nov 17, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-20
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| intel | ax210 firmware | cpe:2.3:o:intel:ax210_firmware |
| intel | ax210 | cpe:2.3:h:intel:ax210 |
| intel | ax201 firmware | cpe:2.3:o:intel:ax201_firmware |
| intel | ax201 | cpe:2.3:h:intel:ax201 |
| intel | ax200 firmware | cpe:2.3:o:intel:ax200_firmware |
| intel | ax200 | cpe:2.3:h:intel:ax200 |
| intel | ac 9560 firmware | cpe:2.3:o:intel:ac_9560_firmware |
| intel | ac 9560 | cpe:2.3:h:intel:ac_9560 |
| intel | ac 9462 firmware | cpe:2.3:o:intel:ac_9462_firmware |
| intel | ac 9462 | cpe:2.3:h:intel:ac_9462 |
| intel | ac 9461 firmware | cpe:2.3:o:intel:ac_9461_firmware |
| intel | ac 9461 | cpe:2.3:h:intel:ac_9461 |
and 13 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel 7265 firmwarebefore 22.40
- intel 9260 firmwareall versions
- intel ac 3165 firmwarebefore 22.40
- intel ac 3168 firmwarebefore 22.40
- intel ac 8260 firmwarebefore 22.40
- intel ac 8265 firmwarebefore 22.40
- intel ac 9260 firmwarebefore 22.40
- intel ac 9461 firmwarebefore 22.40
- intel ac 9462 firmwarebefore 22.40
- intel ac 9560 firmwarebefore 22.40
- intel ax200 firmwarebefore 22.40
- intel ax201 firmwarebefore 22.40
- intel ax210 firmwarebefore 22.40
Versions reported by the vendor
Affected version ranges reported by the assigning authority (intel). Independent of NVD's CPE analysis and usually ahead of it.
n/a Intel(R) PROSet/Wireless WiFi in UEFI
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.3 | kernel-firmware | before 20210208-150300.4.7.1 | 20210208-150300.4.7.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | kernel-firmware | before 20200107-150100.3.31.1 | 20200107-150100.3.31.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | kernel-firmware | before 20210208-150300.4.7.1 | 20210208-150300.4.7.1 |
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-0078Improper input validation in software for some Intel(R) PROSet/Wireless WiFi and Killer(TM) WiFi in Windows 10 may allow an unauthenticated 32Monitor
- CVE-2021-0151Improper access control in the installer for some Intel(R) Wireless Bluetooth(R) and Killer(TM) Bluetooth(R) products in Windows 10 may allo31Monitor
- CVE-2021-0082Uncontrolled search path in software installer for Intel(R) PROSet/Wireless WiFi in Windows 10 may allow an authenticated user to potentiall31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-0065Nov 17, 2021 · Incorrect default permissions in the Intel(R) PROSet/Wireless WiFi software installer for Windows 10 before version 22.40 may allow an authe31Monitor
- ← EarlierCVE-2021-0069Nov 17, 2021 · Improper input validation in firmware for some Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windo26Monitor
- Later →CVE-2021-0075Nov 17, 2021 · Out-of-bounds write in firmware for some Intel(R) PROSet/Wireless WiFi in multiple operating systems and some Killer(TM) WiFi in Windows 10 22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:kernel-firmware | 20210208-150300.4.7.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:kernel-firmware | 20210208-150300.4.7.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.