CVE-2022-38399
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 protection mechanism for alternate hardware interface in SmaCam CS-QR10 all versions and SmaCam Night Vision CS-QR20 all versions allows an attacker to execute an arbitrary OS command by having the product connect to the product's specific serial connection
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 · moderate confidenceThe SmaCam CS-QR10 and CS-QR20 cameras have an unprotected serial connection interface that allows an attacker with physical access to the device's serial pins to execute arbitrary OS commands. The firmware lacks authentication or access controls on this alternate hardware interface.
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 versionsall 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/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 device modelLocate the product label on the camera body or check the device's system information page. Confirm the model is either CS-QR10 or CS-QR20 from Planex (also sold as SmaCam).Affected if The device is a Planex CS-QR10 or CS-QR20 camera (any firmware version)
-
Locate serial header pinsOpen the camera casing and inspect the main circuit board for a 4-6 pin header row (typically labeled J1, CON1, or similar). This is the serial debug interface usually located near the edge of the PCB.Affected if A serial pin header is present and physically accessible on the device board
-
Verify serial console is activeConnect a USB-to-TTL adapter (TX, RX, GND) to the serial pins and open a terminal at 115200 baud. Power on the device and observe if a root shell prompt or boot logs appear without any password prompt.Affected if Serial console provides direct shell access without authentication prompt
-
Check for serial authentication in firmwareIf you have access to the firmware binary, extract it and search for strings related to serial login, password prompts, or UART authentication. Compare against known vulnerable firmware images.Affected if No password or authentication routine is found in the firmware for serial access
You are affected if you own a Planex CS-QR10 or CS-QR20 camera and the serial pins on the circuit board are physically accessible without any authentication barrier.
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 dataRestrict serial interface access through firmware-based password authentication or disable serial after initial setup; for critical deployments, consider network isolation and physical security to limit exposure to this attack vector.
- Consultation8.0 h
- Implementation40.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $20,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-38399 — 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-38399 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