LiveActive security incident?Get immediate response
CVE Record

CVE-2019-1010293: Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Boundary crossing.

Linaro/OP-TEE OP-TEE 3.3.0 and earlier is affected by: Boundary crossing. The impact is: Memory corruption of the TEE itself. The component is: optee_os. The fixed version is: 3.4.0 and later.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2019-1010293 affects OP-TEE 3.3.0 and earlier. The reported issue can corrupt memory inside the Trusted Execution Environment, the security layer many embedded systems use to protect secrets and trusted applications. The fixed version is OP-TEE 3.4.0 or later.

Executive priority

Treat this as a targeted firmware risk. It is most urgent for products where OP-TEE protects keys, identity, payment, boot, or trusted-application workflows. Business urgency depends on whether affected OP-TEE versions are present in deployed devices.

Technical view

The CVE describes a boundary-crossing flaw in optee_os affecting Linaro/OP-TEE OP-TEE 3.3.0 and earlier. Impact is stated as memory corruption of the TEE itself. The bundle names one upstream fix commit and identifies 3.4.0 and later as fixed.

Likely exposure

Exposure is limited to systems, firmware, or products that include OP-TEE 3.3.0 or earlier. The source bundle does not identify downstream device vendors, SoCs, distributions, or deployed product lines.

Exploitation context

No source in the bundle reports active exploitation, and KEV is false. The bundle also does not provide public exploit details, exploit prerequisites, or attack path information.

Researcher notes

Evidence is sparse. The CVE record names boundary crossing and TEE memory corruption, but provides no CVSS, CWE, exploit status, or downstream product mapping. The upstream commit is the main technical reference.

Mitigation direction

  • Inventory firmware and products that include OP-TEE.
  • Upgrade affected OP-TEE builds to 3.4.0 or later.
  • Check OEM or SoC vendor firmware guidance for downstream fixes.
  • Prioritize systems where OP-TEE protects secrets or trusted applications.

Validation and detection

  • Confirm the OP-TEE version from firmware manifests, SBOMs, or build records.
  • Verify vendor firmware includes the upstream fixed version or fix commit.
  • Review trusted-application regression results after firmware update.
  • Document any devices still tied to OP-TEE 3.3.0 or earlier.
Prepared
Confidence
medium
Sources
3

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-2019-1010293 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Linaro/OP-TEEOP-TEE3.3.0 and earlier [fixed: 3.4.0 and later]Listed
Weakness

CWE details

No CWE listed

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