CVE-2022-43779: A potential Time-of-Check to Time-of-Use (TOCTOU) vulnerability has been identified in certain HP PC products using AMI UEFI Firmware (syste
Noroxi assessment
Priority: Monitor (action score 28/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.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- 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
A potential Time-of-Check to Time-of-Use (TOCTOU) vulnerability has been identified in certain HP PC products using AMI UEFI Firmware (system BIOS) which might allow arbitrary code execution, denial of service, and information disclosure. AMI has released updates to mitigate the potential vulnerability.
- Published
- Feb 12, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-367
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- No fixed version yet
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 |
|---|---|---|
| hp | 348 g4 firmware | cpe:2.3:o:hp:348_g4_firmware |
| hp | 348 g4 | cpe:2.3:h:hp:348_g4 |
| hp | 260 g2 desktop mini firmware | cpe:2.3:o:hp:260_g2_desktop_mini_firmware |
| hp | 260 g2 desktop mini | cpe:2.3:h:hp:260_g2_desktop_mini |
| hp | 218 pro g5 mt firmware | cpe:2.3:o:hp:218_pro_g5_mt_firmware |
| hp | 218 pro g5 mt | cpe:2.3:h:hp:218_pro_g5_mt |
| hp | 260 g3 desktop mini firmware | cpe:2.3:o:hp:260_g3_desktop_mini_firmware |
| hp | 260 g3 desktop mini | cpe:2.3:h:hp:260_g3_desktop_mini |
| hp | 260 g4 desktop mini firmware | cpe:2.3:o:hp:260_g4_desktop_mini_firmware |
| hp | 260 g4 desktop mini | cpe:2.3:h:hp:260_g4_desktop_mini |
| hp | 280 g3 microtower pc firmware | cpe:2.3:o:hp:280_g3_microtower_pc_firmware |
| hp | 280 g3 microtower pc | cpe:2.3:h:hp:280_g3_microtower_pc |
and 38 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hp 218 pro g5 mt firmwarebefore f15
- hp 260 g2 desktop mini firmwarebefore 2.26
- hp 260 g3 desktop mini firmwarebefore 02.20.00
- hp 260 g4 desktop mini firmwarebefore 02.12.00
- hp 280 g3 microtower pc firmwarebefore 02.02.40
- hp 280 g3 pci microtower pc firmwarebefore 02.02.40
- hp 288 pro g3 microtower pc firmwarebefore 00.02.40
- hp 290 g1 microtower firmwarebefore 00.02.40
- hp 348 g4 firmwarebefore f.65
- hp desktop pro 300 g3 firmwarebefore f15
- hp desktop pro a 300 g3 firmwarebefore f12
- hp desktop pro a g2 firmwarebefore f.11
- hp desktop pro a g2 microtower firmwarebefore f.11
- hp desktop pro a g3 firmwarebefore f12
- hp desktop pro a g3 microtower firmwarebefore f12
- hp desktop pro g3 firmwarebefore f15
- hp desktop pro g3 microtower firmwarebefore f15
- hp desktop pro microtower firmwarebefore 00.02.40
- hp rp2 retail system 2000 firmwarebefore 2.24
- hp rp2 retail system 2020 firmwarebefore 2.24
Versions reported by the vendor
Affected version ranges reported by the assigning authority (hp). Independent of NVD's CPE analysis and usually ahead of it.
HP Inc. HP PC products using AMI UEFI Firmware
- See HP Security Bulletin reference for affected versions.affected
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.
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
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race ConditionCVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/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.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.