CVE-2021-0092: Improper access control in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable a denial of service…
Noroxi assessment
Priority: Monitor (action score 17/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.24% (FIRST EPSS).
- Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
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 access control in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable a denial of service via local access.
- Published
- Feb 9, 2022
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-400
Report tools
Action score
17
Low priority for now.
- CVSS
- 17 / 40 · 4.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 | atom c3308 | cpe:2.3:h:intel:atom_c3308 |
| intel | atom c3336 | cpe:2.3:h:intel:atom_c3336 |
| intel | atom c3338 | cpe:2.3:h:intel:atom_c3338 |
| intel | atom c3338r | cpe:2.3:h:intel:atom_c3338r |
| intel | atom c3436l | cpe:2.3:h:intel:atom_c3436l |
| intel | atom c3508 | cpe:2.3:h:intel:atom_c3508 |
| intel | atom c3538 | cpe:2.3:h:intel:atom_c3538 |
| intel | atom c3558 | cpe:2.3:h:intel:atom_c3558 |
| intel | atom c3558r | cpe:2.3:h:intel:atom_c3558r |
| intel | atom c3708 | cpe:2.3:h:intel:atom_c3708 |
| intel | atom c3750 | cpe:2.3:h:intel:atom_c3750 |
| intel | atom c3758 | cpe:2.3:h:intel:atom_c3758 |
and 188 more
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) Processors
- See referencesaffected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel atom c3308all versions
- intel atom c3336all versions
- intel atom c3338all versions
- intel atom c3338rall versions
- intel atom c3436lall versions
- intel atom c3508all versions
- intel atom c3538all versions
- intel atom c3558all versions
- intel atom c3558rall versions
- intel atom c3708all versions
- intel atom c3750all versions
- intel atom c3758all versions
- intel atom c3758rall versions
- intel atom c3808all versions
- intel atom c3830all versions
- intel atom c3850all versions
- intel atom c3858all versions
- intel atom c3950all versions
- intel atom c3955all versions
- intel atom c3958all versions
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-0099Insufficient control flow management in the firmware for some Intel(R) Processors may allow an authenticated user to potentially enable an…31Monitor
- CVE-2021-0091Improper access control in the firmware for some Intel(R) Processors may allow an unauthenticated user to potentially enable an escalation…31Monitor
- CVE-2022-0002Non-transparent sharing of branch predictor within a context in some Intel(R) Processors may allow an authorized user to potentially enable…26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2020-24513Jun 9, 2021 · Domain-bypass transient execution vulnerability in some Intel Atom(R) Processors may allow an authenticated user to potentially enable…26Monitor
- Later →CVE-2021-0093Feb 9, 2022 · Incorrect default permissions in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable a denial of…17Monitor
- Later →CVE-2021-0103Feb 9, 2022 · Insufficient control flow management in the firmware for some Intel(R) Processors may allow a privileged user to potentially enable an…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.