CVE-2022-35733
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 · uneditedMissing authentication for critical function vulnerability in UNIMO Technology digital video recorders (UDR-JA1004/JA1008/JA1016 firmware versions v1.0.20.13 and earlier, and UDR-JA1016 firmware versions v2.0.20.13 and earlier) allows a remote unauthenticated attacker to execute an arbitrary OS command by sending a specially crafted request to the affected device web interface.
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 confidenceMissing authentication vulnerability in UNIMO Technology UDR-JA1004/JA1008/JA1016 digital video recorders allows remote unauthenticated attackers to execute arbitrary OS commands via specially crafted requests to the web interface. The vulnerability affects firmware versions v1.0.20.13 and earlier (JA1004/JA1008/JA1016) and v2.0.20.13 and earlier (JA1016), enabling full system compromise without credentials.
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 data<= 1.0.20.13<= 1.0.20.13<= 2.0.20.13CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 device modelLocate the physical device label or access the DVR web interface to confirm the model is UDR-JA1004, UDR-JA1008, or UDR-JA1016. Check the device documentation or system information page for the exact model designation.Affected if The device is not one of the three affected UNIMO models (JA1004, JA1008, JA1016).
-
Determine the firmware versionAccess the DVR system settings or about page via the web interface, or use the vendor's diagnostic tool if available, to retrieve the installed firmware version number.Affected if The firmware version is v1.0.20.13 or earlier for JA1004/JA1008/JA1016, or v2.0.20.13 or earlier for JA1016.
-
Verify the web interface is accessibleAttempt to access the DVR web interface using its IP address on common HTTP ports (80, 8080, 443). Confirm the device responds to HTTP requests without requiring authentication.Affected if The web interface is exposed and responds to unauthenticated requests.
-
Check network exposure of the deviceReview firewall rules, NAT configurations, or network segmentation to determine if the DVR web interface IP is accessible from untrusted networks or the public internet.Affected if The device web interface is reachable from networks outside the trusted internal network.
A user is affected if they have a UNIMO UDR-JA1004, JA1008, or JA1016 device running firmware at or below the affected version with the web interface accessible from their network.
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 dataApply vendor-provided firmware updates to remediate this vulnerability. If patches are unavailable, restrict network access to the device web interface using firewall rules or VLAN segmentation to limit exposure to trusted networks only.
- Consultation6.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35733 — 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-35733 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