Security readout for executives and security teams
Plain-English summary
CVE-2022-2347 is a memory corruption flaw in U-Boot’s USB DFU handling. A physically present attacker could abuse malformed DFU traffic to overwrite memory beyond an allocated buffer. The issue is high severity because successful exploitation could affect confidentiality, integrity, and availability, but the cited evidence points to local physical access, high complexity, and user interaction.
Executive priority
Treat this as high priority for embedded fleets where attackers, contractors, customers, or supply-chain actors may physically access devices. For devices in controlled facilities with locked boot paths and no accessible DFU workflow, urgency is lower but still requires inventory and vendor-update tracking.
Technical view
The U-Boot DFU implementation does not bound a USB DFU download setup packet length field and does not verify transfer direction against the command. A wLength value above the intended request buffer size can cause a heap overflow. The provided CVSS is 7.7, with local attack vector, high complexity, no privileges, user interaction required, and changed scope.
Likely exposure
Exposure is most likely in embedded devices, appliances, or systems using U-Boot with USB DFU functionality reachable during boot or recovery workflows. The provided affected version data is unspecified, so product-specific exposure must be confirmed through vendor advisories, firmware SBOMs, or bootloader build records.
Exploitation context
The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation requires local physical access and interaction with USB DFU behavior, which reduces broad internet-scale risk but matters for field-deployed, unattended, or high-value devices.
Researcher notes
The CVE data gives strong root-cause detail but incomplete affected-version boundaries. Avoid assuming all U-Boot deployments are exposed. Focus analysis on DFU enablement, board configuration, firmware lineage, vendor patches, and whether physical USB recovery paths are reachable outside trusted maintenance procedures.
Mitigation direction
- Check U-Boot, OS, and device-vendor advisories for applicable fixed firmware or package updates.
- Apply Debian LTS or vendor firmware updates where they are relevant to deployed assets.
- Restrict physical access to USB ports, recovery modes, and bootloader interfaces.
- Disable or lock USB DFU in production where vendor-supported and operationally safe.
- Prioritize compensating controls for unattended, public, or supply-chain-exposed devices.
Validation and detection
- Inventory devices and firmware builds that include U-Boot USB DFU support.
- Map deployed products against CVE, Debian LTS, Siemens, and vendor-specific advisories.
- Confirm whether USB DFU or bootloader recovery is accessible in production configurations.
- Verify update status through firmware versions, package records, or vendor management tools.
- Document unresolved devices with physical exposure and compensating controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-2347 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H16GoogleVulnerability scoring details
Base CVSS 3.1 score
7.7HighVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://seclists.org/oss-sec/2022/q3/41CVE reference, Google · x_refsource_MISC
- https://lists.debian.org/debian-lts-announce/2025/05/msg00001.htmlCVE reference, CVE
- https://cert-portal.siemens.com/productcert/html/ssa-577017.htmlCVE reference, siemens-SADP
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.