CVE-2023-38290
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-38290 is a high-severity Improper Physical Access Control (CWE-1263) vulnerability in Defcon (inferred from references). Its CVSS base score is 7.8 (High).
Operationally, ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to PE-2 (Physical Access Authorizations) and PE-3 (Physical Access Control) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-42109
Vulnerability Data
Certain software builds for the BLU View 2 and Sharp Rouvo V Android devices contain a vulnerable pre-installed app with a package name of com.evenwell.fqc (versionCode='9020801', versionName='9.0208.01' ; versionCode='9020913', versionName='9.0209.13' ; versionCode='9021203', versionName='9.0212.03') that allows local third-party apps to execute…
more
arbitrary shell commands in its context (system user) due to inadequate access control. No permissions or special privileges are necessary to exploit the vulnerability in the com.evenwell.fqc app. No user interaction is required beyond installing and running a third-party app. The vulnerability allows local apps to access sensitive functionality that is generally restricted to pre-installed apps, such as programmatically performing the following actions: granting arbitrary permissions (which can be used to obtain sensitive user data), installing arbitrary apps, video recording the screen, wiping the device (removing the user's apps and data), injecting arbitrary input events, calling emergency phone numbers, disabling apps, accessing notifications, and much more. The software build fingerprints for each confirmed vulnerable device are as follows: BLU View 2 (BLU/B131DL/B130DL:11/RP1A.200720.011/1672046950:user/release-keys, BLU/B131DL/B130DL:11/RP1A.200720.011/1663816427:user/release-keys, BLU/B131DL/B130DL:11/RP1A.200720.011/1656476696:user/release-keys, BLU/B131DL/B130DL:11/RP1A.200720.011/1647856638:user/release-keys) and Sharp Rouvo V (SHARP/VZW_STTM21VAPP/STTM21VAPP:12/SP1A.210812.016/1KN0_0_460:user/release-keys and SHARP/VZW_STTM21VAPP/STTM21VAPP:12/SP1A.210812.016/1KN0_0_530:user/release-keys). This malicious app starts an exported activity named com.evenwell.fqc/.activity.ClickTest, crashes the com.evenwell.fqc app by sending an empty Intent (i.e., having not extras) to the com.evenwell.fqc/.FQCBroadcastReceiver receiver component, and then it sends command arbitrary shell commands to the com.evenwell.fqc/.FQCService service component which executes them with "system" privileges.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Directly enforces physical access authorizations at entry points to restricted areas.
Maintains the authorized physical access list that the system must enforce.
Monitors physical access to detect unauthorized entry after the fact.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.7.1 directly defines, builds and maintains physical perimeters that stop unauthorized physical actors from reaching the protected assets, which is the exact scenario CWE-1263 names; the bounded remainder is logical-only access-control flaws inside the perimeter that physical barriers never touch.
A.7.14 addresses secure sanitization and label removal of equipment/media being disposed or reused to stop information leakage; it has no bearing on whether a product sufficiently restricts physical access to protected areas during normal operation, so the weakness can still be present and exploitable.
A.7.2 directly mandates physical access controls (authentication, monitoring, restricted areas, visitor supervision, delivery segregation) that stop unauthorized physical actors from exploiting the weakness; the bounded remainder is non-physical vectors (e.g. remote side-channels or supply-chain tampering before delivery) that the clause explicitly isolates from its scope.
A.7.3 directly mandates physical siting, shielding, visibility controls and non-disclosure of facility locations that stop unauthorized physical actors from reaching the protected information, closing the dominant slice of CWE-1263; the bounded remainder is design-level logical access-control flaws inside the product itself that physical-facility measures do not reach.
A weakness discoverable only by hardware development or microarchitectural research (HARDWARE_ONLY_CWES) grades `finds` none against a software-development control: the frameworks we grade do not reach hardware development (owner, 2026-10-16).
A.7.6 directly mandates physical measures (no unsupervised work, locking/inspecting vacant areas, banning unauthorized recording devices, controlling endpoint devices) that stop an unauthorized actor with physical presence from interfering with or extracting the restricted information, leaving only a bounded remainder (e.g. sophisticated insider bypassing all procedural/physical barriers, or non-area-based physical attacks like emanations).
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-1263, a class-level weakness, and none of its children carries one either.