LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38828: Xiongmai Camera XM-JPR2-LX V4.02.R12.A6420987.10002.147502.00000 is vulnerable to plain-text traffic sniffing.

Xiongmai Camera XM-JPR2-LX V4.02.R12.A6420987.10002.147502.00000 is vulnerable to plain-text traffic sniffing.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE means a specific Xiongmai camera firmware may send traffic without encryption, allowing someone on a nearby network path to read sensitive communications. The business risk is confidentiality exposure, not system takeover, data modification, or outage based on the provided CVSS data.

Executive priority

Treat as a targeted confidentiality issue for camera networks. Prioritize if these devices handle sensitive locations, shared networks, or remote management. It is not presented as actively exploited or business-critical from the supplied sources.

Technical view

CVE-2021-38828 is a CWE-319 cleartext transmission issue in Xiongmai Camera XM-JPR2-LX firmware V4.02.R12.A6420987.10002.147502.00000. CVSS 3.1 is 5.3 with adjacent-network attack vector, high complexity, no privileges, no user interaction, and high confidentiality impact only.

Likely exposure

Exposure appears limited to organizations running the named Xiongmai XM-JPR2-LX camera firmware where attackers can observe adjacent network traffic. The bundle does not provide CPEs, broader affected versions, or vendor-maintained affected-product data.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is traffic confidentiality loss through sniffing, with adjacent-network positioning and high attack complexity per the CVSS vector.

Researcher notes

The record is sparse: affected fields are listed as n/a, but the title and description name one model and firmware. Do not expand scope without vendor evidence. CVSS indicates adjacent access, high attack complexity, and confidentiality-only impact.

Mitigation direction

  • Check Xiongmai or device supplier guidance for firmware updates or official mitigations.
  • Inventory cameras and identify the exact model and firmware version.
  • Place affected cameras on restricted, monitored network segments.
  • Avoid sending sensitive credentials or management traffic over untrusted networks.
  • Require VPN or encrypted access paths where supported by the environment.

Validation and detection

  • Confirm whether any deployed camera matches XM-JPR2-LX and the listed firmware version.
  • Review network placement for adjacent-user access to camera traffic.
  • Verify whether camera management and operational traffic is encrypted in a controlled lab.
  • Check vendor, reseller, or maintainer advisories for firmware status.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-319: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2021-38828 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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
2Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-38828Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
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-319 · source CWE mapping

Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.