CVE-2022-0005: Sensitive information accessible by physical probing of JTAG interface for some Intel(R) Processors with SGX may allow an unprivileged user
Noroxi assessment
Priority: Monitor (action score 9/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.20% (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: microcode_ctl (Red Hat:enterprise_linux:9::baseos) 4:20220809-1.el9.
Low priority for now. Upgrade to microcode_ctl (Red Hat:enterprise_linux:9::baseos) 4:20220809-1.el9 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
Sensitive information accessible by physical probing of JTAG interface for some Intel(R) Processors with SGX may allow an unprivileged user to potentially enable information disclosure via physical access.
- Published
- May 12, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-319
Report tools
Action score
9
Monitor
Low priority for now.
- CVSS
- 9 / 40 · 2.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
- 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 | celeron g5205u firmware | cpe:2.3:o:intel:celeron_g5205u_firmware |
| intel | celeron g5205u | cpe:2.3:h:intel:celeron_g5205u |
| intel | celeron g5305u firmware | cpe:2.3:o:intel:celeron_g5305u_firmware |
| intel | celeron g5305u | cpe:2.3:h:intel:celeron_g5305u |
| intel | celeron g5900 firmware | cpe:2.3:o:intel:celeron_g5900_firmware |
| intel | celeron g5900 | cpe:2.3:h:intel:celeron_g5900 |
| intel | celeron g5900t firmware | cpe:2.3:o:intel:celeron_g5900t_firmware |
| intel | celeron g5900t | cpe:2.3:h:intel:celeron_g5900t |
| intel | celeron g5905 firmware | cpe:2.3:o:intel:celeron_g5905_firmware |
| intel | celeron g5905 | cpe:2.3:h:intel:celeron_g5905 |
| intel | celeron g5905t firmware | cpe:2.3:o:intel:celeron_g5905t_firmware |
| intel | celeron g5905t | cpe:2.3:h:intel:celeron_g5905t |
and 188 more
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- intel celeron g5205u firmwareall versions
- intel celeron g5305u firmwareall versions
- intel celeron g5900 firmwareall versions
- intel celeron g5900t firmwareall versions
- intel celeron g5905 firmwareall versions
- intel celeron g5905t firmwareall versions
- intel celeron g5920 firmwareall versions
- intel celeron g5925 firmwareall versions
- intel celeron n5095 firmwareall versions
- intel celeron n5100 firmwareall versions
- intel celeron n5105 firmwareall versions
- intel core i3-10100 firmwareall versions
- intel core i3-10100e firmwareall versions
- intel core i3-10100f firmwareall versions
- intel core i3-10100t firmwareall versions
- intel core i3-10100te firmwareall versions
- intel core i3-10100y firmwareall versions
- intel core i3-10105 firmwareall versions
- intel core i3-10105f firmwareall versions
- intel core i3-10105t 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 with SGX
- See referencesaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:enterprise_linux:9::baseos | microcode_ctl | before 4:20220809-1.el9 | 4:20220809-1.el9 |
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 |
|---|---|---|
| red hat:microcode_ctl | 4:20220809-1.el9 · Red Hat:enterprise_linux:9::baseos | 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.
No history yet (it accumulates with the daily EPSS job).
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
- 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
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-319 · Cleartext Transmission of Sensitive InformationCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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)
ATT&CK techniques
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.