Security readout for executives and security teams
Plain-English summary
This vulnerability affects Blurams Lumi Security Camera A31C firmware v2.3.38.12558 and could let someone with physical proximity run arbitrary code on the device. Business urgency is moderate because exploitation appears to require nearby physical access, but a compromised camera can affect confidentiality, integrity, and availability.
Executive priority
Prioritize as a moderate operational risk for sites using this exact camera model. The issue is not presented as remotely exploitable, but public research and high device-impact scoring justify prompt inventory, physical-access review, and vendor remediation checks.
Technical view
CVE-2023-51820 is described as CWE-94 code injection/arbitrary code execution in Blurams Lumi Security Camera A31C v2.3.38.12558. The CVSS 3.1 vector is AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, meaning physical access, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely where Blurams Lumi A31C cameras running firmware v2.3.38.12558 are deployed in physically accessible areas. CVE metadata does not provide complete vendor/product CPE entries, so inventory may require manual device and firmware checks.
Exploitation context
The source bundle includes a public research write-up and a GitHub PoC reference. It does not show CISA KEV listing or confirmed active exploitation. Treat public technical detail as increasing validation urgency, while recognizing the physical-access requirement limits broad remote exposure.
Researcher notes
The CVE record lacks structured affected CPE data and names affected product details mainly in the description. Avoid broad product assumptions. Public PoC material exists, but this assessment intentionally avoids exploit procedure and relies on CVSS, CWE, KEV status, and cited references.
Mitigation direction
- Identify Blurams Lumi A31C cameras in all managed locations.
- Check whether devices run firmware v2.3.38.12558.
- Restrict physical access to deployed cameras and mounting points.
- Check Blurams or reseller guidance for firmware updates or remediation.
- Replace or isolate devices if no vendor fix is available.
Validation and detection
- Confirm model and firmware from device administration records or console.
- Prioritize cameras in public, shared, or visitor-accessible areas.
- Review network logs for unusual camera behavior after physical access events.
- Document whether vendor guidance or updated firmware exists.
- Track remediation status per camera asset.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution 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 lookupCVE-2023-51820 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H0.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.