Security readout for executives and security teams
Plain-English summary
CVE-2022-34150 affects MiCODUS MV720 GPS trackers. A logged-in user may be able to reference arbitrary device IDs on the main web server and view another device’s sensitive information because ownership is not properly checked.
Executive priority
Treat this as a high-priority privacy and tracking-data exposure risk where MV720 devices monitor vehicles, personnel, or sensitive assets. Prioritize inventory, vendor guidance, and exposure reduction.
Technical view
The issue is an authenticated insecure direct object reference mapped to CWE-639. The affected endpoint and device ID parameter accept user-controlled device IDs without further authorization verification. CVSS 3.1 is 7.1: network exploitable, low complexity, low privileges, no user interaction, high confidentiality impact, low integrity impact.
Likely exposure
Organizations using MiCODUS MV720 devices or the associated main web server are potentially exposed. The source bundle lists all MV720 versions as affected and does not identify unaffected versions.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle. Evidence supports a plausible authenticated abuse path, but the provided sources do not claim active exploitation or provide exploit status.
Researcher notes
The core control failure is missing per-object authorization on device identifiers after authentication. Do not assume a patch exists from the supplied evidence; track vendor and CISA advisory updates before declaring remediation complete.
Mitigation direction
- Check MiCODUS and CISA guidance for fixed versions or official mitigations.
- Restrict web portal access to trusted users and networks where possible.
- Review whether MV720 tracking is acceptable for sensitive assets.
- Ask the vendor how device ownership authorization is enforced.
- Monitor for unusual access to device IDs across accounts.
Validation and detection
- Inventory all MiCODUS MV720 devices and related web accounts.
- Confirm whether the main MiCODUS web server is used operationally.
- Review logs for authenticated users accessing unrelated device IDs.
- Validate vendor remediation status before accepting continued exposure.
- Document any compensating controls around portal access.
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-639: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2022-34150 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
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
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:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/uscert/ics/advisories/icsa-22-200-01CVE reference · x_refsource_CONFIRM
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.