Hardware allows activation of test or debug logic at runtime for some Intel(R) processors which may allow an unauthenticated user to potenti
Noroxi assessment
Priority: Monitor (action score 27/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.43% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: intel-ucode (Alpine:v3.13) 20220207-r0; ucode-intel (openSUSE:Leap 15.3) 20220207-10.1; ucode-intel (openSUSE:Tumbleweed) 20220207-1.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to intel-ucode (Alpine:v3.13) 20220207-r0; ucode-intel (openSUSE:Leap 15.3) 20220207-10.1; ucode-intel (openSUSE:Tumbleweed) 20220207-1.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
Hardware allows activation of test or debug logic at runtime for some Intel(R) processors which may allow an unauthenticated user to potentially enable escalation of privilege via physical access.
- Published
- Nov 17, 2021
- Updated
- Oct 8, 2026
- EPSS
- 0.4% · 36th percentile
- CWE
- —
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
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
- 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 | pentium j6426 firmware | cpe:2.3:o:intel:pentium_j6426_firmware |
| intel | pentium j6426 | cpe:2.3:h:intel:pentium_j6426 |
| intel | pentium j4205 firmware | cpe:2.3:o:intel:pentium_j4205_firmware |
| intel | pentium j4205 | cpe:2.3:h:intel:pentium_j4205 |
| intel | pentium j3710 firmware | cpe:2.3:o:intel:pentium_j3710_firmware |
| intel | pentium j3710 | cpe:2.3:h:intel:pentium_j3710 |
| intel | pentium j2900 firmware | cpe:2.3:o:intel:pentium_j2900_firmware |
| intel | pentium j2900 | cpe:2.3:h:intel:pentium_j2900 |
| intel | pentium j2850 firmware | cpe:2.3:o:intel:pentium_j2850_firmware |
| intel | pentium j2850 | cpe:2.3:h:intel:pentium_j2850 |
| intel | celeron j6412 firmware | cpe:2.3:o:intel:celeron_j6412_firmware |
| intel | celeron j6412 | cpe:2.3:h:intel:celeron_j6412 |
and 132 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel atom c3000 firmwareall versions
- intel atom x5-e3930 firmwareall versions
- intel atom x5-e3940 firmwareall versions
- intel atom x7-e3950 firmwareall versions
- intel celeron j1750 firmwareall versions
- intel celeron j1800 firmwareall versions
- intel celeron j1850 firmwareall versions
- intel celeron j1900 firmwareall versions
- intel celeron j3060 firmwareall versions
- intel celeron j3160 firmwareall versions
- intel celeron j3355 firmwareall versions
- intel celeron j3355e firmwareall versions
- intel celeron j3455 firmwareall versions
- intel celeron j3455e firmwareall versions
- intel celeron j4005 firmwareall versions
- intel celeron j4025 firmwareall versions
- intel celeron j4105 firmwareall versions
- intel celeron j4125 firmwareall versions
- intel celeron j6412 firmwareall versions
- intel celeron j6413 firmwareall versions
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 which
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.13 | intel-ucode | before 20220207-r0 | 20220207-r0 |
| openSUSE:Leap 15.3 | ucode-intel | before 20220207-10.1 | 20220207-10.1 |
| openSUSE:Tumbleweed | ucode-intel | before 20220207-1.1 | 20220207-1.1 |
| SUSE:HPE Helion OpenStack 8 | ucode-intel | before 20220207-13.93.1 | 20220207-13.93.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | ucode-intel | before 20220207-3.206.1 | 20220207-3.206.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | ucode-intel | before 20220207-3.70.1 | 20220207-3.70.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | ucode-intel | before 20220207-10.1 | 20220207-10.1 |
| SUSE:Linux Enterprise Server 12 SP5 | ucode-intel | before 20220207-3.38.1 | 20220207-3.38.1 |
Same product
intel: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-43505Insufficient control flow management in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable den17Monitor
- CVE-2022-27879Improper buffer restrictions in the BIOS firmware for some Intel(R) Processors may allow a privileged user to potentially enable information17Monitor
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 |
|---|---|---|
| alpine:intel-ucode | 20220207-r0 · Alpine:v3.13 | Package registry (OSV) |
| opensuse:ucode-intel | 20220207-10.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| suse:ucode-intel | 20220207-3.70.1 · SUSE:Linux Enterprise High Performance Computing 15-ESPOS | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-21-0930 · Nov 18, 2021(Intel Güvenlik Zafiyeti)
Technical details
Attack conditions
- Physical access to the device is required.
- 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
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:P/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.