LiveActive security incident?Get immediate response
CVE Record

CVE-2022-34835: In Das U-Boot through 2022.07-rc5, an integer signedness error and resultant stack-based buffer overflow in...

In Das U-Boot through 2022.07-rc5, an integer signedness error and resultant stack-based buffer overflow in the "i2c md" command enables the corruption of the return address pointer of the do_i2c_md function.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This issue is in Das U-Boot, a bootloader used in embedded systems. A malformed use of the documented I2C memory-display command can corrupt stack memory in affected builds. Business urgency depends on whether your devices expose U-Boot command access.

Executive priority

Treat this as inventory-driven priority. Escalate for products where U-Boot command access is reachable by users, technicians, or attackers with physical access; otherwise handle through normal firmware maintenance.

Technical view

CVE-2022-34835 describes an integer signedness error causing a stack-based buffer overflow in the U-Boot `i2c md` command, corrupting the return address pointer in `do_i2c_md`. The bundle identifies affected scope as Das U-Boot through 2022.07-rc5 and points to an upstream commit.

Likely exposure

Exposure is most likely in embedded, industrial, or appliance firmware that includes U-Boot through 2022.07-rc5 and permits bootloader command access. The bundle does not provide a complete vendor/product affected list.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Practical risk appears tied to local or otherwise privileged access to the U-Boot command environment.

Researcher notes

The evidence supports root cause, affected upstream range, and fix reference, but lacks CVSS, CWE entries, exploit status, and a complete affected-product matrix. Avoid assuming remote exploitability from the provided sources.

Mitigation direction

  • Inventory firmware and bootloader versions for U-Boot through 2022.07-rc5.
  • Apply vendor firmware updates or builds containing the upstream fix commit.
  • Follow Debian LTS guidance where Debian U-Boot packages are used.
  • Check Siemens ProductCERT guidance for any Siemens-managed assets.
  • Restrict physical and console access to bootloader interfaces.

Validation and detection

  • Confirm whether each device image includes U-Boot and its exact version.
  • Check whether the `i2c md` command is enabled in deployed bootloader environments.
  • Verify the upstream fix commit or a vendor backport is present.
  • Review Debian and Siemens advisories for environment-specific applicability.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2022-34835 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
3Timeline events
2ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.