Loading vulnerability…
CVE-2019-1010298 is a buffer overflow vulnerability in Linaro OP-TEE affecting optee_os in version 3.3.0 and earlier. The available information identifies the flaw only at the component level and does not specify the exact vulnerable function or code path. Successful exploitation can lead to code execution within the Trusted Execution Environment core, i.e., in the context of the TEE kernel.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (PoC) exploit for CVE-2019-1010298 (also referenced as OP-TEE-2018-0011), targeting a vulnerability in an OP-TEE Trusted Application (TA). The structure consists of build scripts (Makefiles, CMake, Android.mk), a host-side exploit in C (host/exploit.c), and the TA implementation (ta/verify.c) with associated headers. The exploit demonstrates how to establish a session with the TA using the OP-TEE client API and invokes a command (TA_ASYMM_VERIFY) that triggers the vulnerable code path. The TA is identified by the UUID 5dbac793-f574-4871-8ad3-04331ec17f24. The code does not include a weaponized payload but serves as a PoC to show how the vulnerability can be reached and potentially exploited. The attack vector is local, requiring code execution on a device with OP-TEE and the vulnerable TA installed. No network endpoints or external IPs are present; the main fingerprintable endpoint is the TA UUID.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.