Vulnerability in TrustedFirmware Open Portable Trusted Execution Environment (CVE-2022-47549)
Summary
Vulnerability in TrustedFirmware Open Portable Trusted Execution Environment (CVE-2022-47549). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
An unprotected memory-access operation in optee_os in TrustedFirmware Open Portable Trusted Execution Environment (OP-TEE) before 3.20 allows a physically proximate adversary to bypass signature verification and install malicious trusted applications via electromagnetic fault injections.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2022-47549 has been found in TrustedFirmware Open Portable Trusted Execution Environment.
Successful exploitation can lead to full system takeover. CVSS score: 6.4/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "TrustedFirmware Open Portable Trusted Execution Environment CVE-2022-47549" on the vendor's site.
CVE-2022-47549 (TrustedFirmware Open Portable Trusted Execution Environment) — CWE-347 / CVSS v3 6.4
Attack vector: physical / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in TrustedFirmware Open Portable Trusted Execution Environment.
Check the vendor advisory for the affected versions of TrustedFirmware Open Portable Trusted Execution Environment.
Severity: Medium (CVSS 6.4/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで TrustedFirmware Open Portable Trusted Execution Environment を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- exploit people.linaro.org