CVE-2022-33944
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe main MiCODUS MV720 GPS tracker web server has an authenticated insecure direct object references vulnerability on endpoint and POST parameter “Device ID,” which accepts arbitrary device IDs.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe MiCODUS MV720 GPS tracker web server contains an authenticated Insecure Direct Object Reference (IDOR) vulnerability. An authenticated user can submit arbitrary Device IDs via POST parameter to access or manipulate data belonging to other devices, because the endpoint does not verify that the authenticated user owns or is authorized to access the specified Device ID.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the Micodus MV720 deviceLocate the GPS tracker hardware or check network inventory for Micodus MV720 devices. The device is typically identified by its MAC address OUI (Organization Unique Identifier) or through the device's web interface login page which often displays the device model.Affected if The device is a Micodus MV720 GPS tracker firmware.
-
Confirm web server is enabledAttempt to access the web interface by entering the device's IP address in a web browser. The default web port is typically 80 or 443. If a login page loads, the web server is active.Affected if The web interface is accessible and requires authentication.
-
Locate the Device ID parameter endpointAfter logging into the web interface, examine the application's POST requests using browser developer tools or a proxy. Look for endpoints that accept a Device ID parameter in the request body, such as /api/device/info or similar API paths.Affected if An endpoint exists that accepts a Device ID via POST parameter.
-
Verify lack of ownership validationWhile authenticated as one user, note your current Device ID. Then submit a request to the identified endpoint with a different Device ID that you do not own. Observe whether the server returns data or allows manipulation of the other device without returning a 403 Forbidden or authorization error.Affected if The server returns data or allows actions on devices without verifying the authenticated user owns the specified Device ID.
If you have a Micodus MV720 with its web server enabled and the identified endpoint accepts Device ID parameters without ownership verification, your environment is affected by CVE-2022-33944.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper object-level authorization checks to verify the authenticated user owns or has permission to access the requested device before processing any request with a Device ID parameter.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-33944 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-33944 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data