LiveActive security incident?Get immediate response
CVE Record

CVE-2018-18068: The ARM-based hardware debugging feature on Raspberry Pi 3 module B+ and possibly other devices allows non-...

The ARM-based hardware debugging feature on Raspberry Pi 3 module B+ and possibly other devices allows non-secure EL1 code to read/write any EL3 (the highest privilege level in ARMv8) memory/register via inter-processor debugging. With a debug host processor A running in non-secure EL1 and a debug target processor B running in any privilege level, the debugging feature allows A to halt B and promote B to any privilege level. As a debug host, A has full control of B even if B owns a higher privilege level than A. Accordingly, A can read/write any EL3 memory/register via B. Also, with this memory access, A can execute arbitrary code in EL3.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a hardware debug weakness where lower-privileged code on an ARM core can control another core at the highest privilege level. If present in deployed devices, it could break the trust boundary protecting secure firmware and secrets. The public record does not name a vendor patch, affected version range, or active exploitation. Exposure appears limited to Raspberry Pi 3 Model B+ and possibly similar ARMv8 devices with the described hardware debugging behavior. The CVE affected-product data is listed as n/a, so asset matching must rely on hardware inventory and vendor confirmation. Treat this as a high-impact but uncertain-scope hardware trust issue. Prioritize asset discovery and vendor confirmation before emergency action. Devices enforcing security boundaries, storing secrets, or running untrusted kernel-level code deserve the earliest review. Mitigation focus: Check Raspberry Pi and SoC vendor guidance for firmware or hardware mitigations.; Inventory Raspberry Pi 3 Model B+ and similar ARMv8 devices in sensitive roles.; Avoid running untrusted kernel-level or EL1 code on affected hardware..

Prepared

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-18068 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
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.