LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40785: Unsanitized input when setting a locale file leads to shell injection in mIPC camera firmware 5.3.1.2003161...

Unsanitized input when setting a locale file leads to shell injection in mIPC camera firmware 5.3.1.2003161406. This allows an attacker to gain remote code execution on cameras running the firmware when a victim logs into a specially crafted mobile app.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-40785 is a high-severity remote code execution issue in mIPC camera firmware 5.3.1.2003161406. Unsanitized locale-file input can lead to shell injection, allowing attacker code execution when the described mobile-app login scenario is met.

Executive priority

Prioritize identification and isolation if these cameras exist in production or sensitive facilities. The issue can enable full device compromise, but current source evidence does not confirm active exploitation or a named patch.

Technical view

The CVE describes CWE-78 command injection caused by unsanitized input while setting a locale file. The published CVSS 3.1 score is 8.8 with network attack vector, low complexity, low privileges, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely limited to cameras running mIPC firmware 5.3.1.2003161406. The CVE affected-product metadata is incomplete, so asset owners should verify device models, firmware lineage, and vendor advisories before assuming broader or narrower impact.

Exploitation context

The CVE references a public exploit-tagged advisory, but the bundle does not show CISA KEV listing or evidence of active exploitation. The described path involves a victim logging into a specially crafted mobile app; do not treat this as confirmed in-the-wild activity.

Researcher notes

Affected-product metadata is sparse despite a specific firmware version in the description. There is also tension between the mobile-app victim scenario and CVSS UI:N; validate the exact attack workflow against the primary advisory.

Mitigation direction

  • Inventory mIPC camera deployments and record exact firmware versions.
  • Check vendor guidance for fixed firmware or supported remediation.
  • Restrict camera administration and app access to trusted users and networks.
  • Segment affected cameras from sensitive systems until exposure is resolved.
  • Avoid using untrusted or unofficial mobile applications with camera accounts.

Validation and detection

  • Confirm whether any cameras run firmware 5.3.1.2003161406.
  • Review procurement and device records for mIPC firmware dependencies.
  • Check vendor release notes for CVE-2022-40785 remediation status.
  • Review camera logs for unusual configuration or locale-setting activity.
  • Validate mobile app sources used by administrators and operators.
Prepared
Confidence
medium
Sources
4

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.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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 lookup
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-2022-40785 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
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-40785Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.