dbcve.org
Pc420 FirmwareOperating system · Govicture

CVE-2023-41612

HIGH · 8.8 CVSS v3.1 Published 2024-09-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

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 · unedited
Victure PC420 1.1.39 was discovered to use a weak encryption key for the file enabled_telnet.dat on the Micro SD card.

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 confidence

The Victure PC420 camera firmware 1.1.39 uses a weak encryption key to protect the enabled_telnet.dat file stored on the Micro SD card. An attacker with physical access to the SD card or who can read its contents can decrypt this file and potentially enable telnet access on the device, creating a remote backdoor.

MitigationUpdate to vendor firmware when available; physically secure the SD card; disable telnet service if possible through device settings; consider network segmentation for affected devices.

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
Pc420 FirmwareOperating system
Affected:= 1.1.39

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the camera is a Victure PC420 model by inspecting the device label, packaging, or administrative interface
    Affected if Device is not a Victure PC420
  2. Check firmware version
    Access the camera's administrative interface or use the vendor-provided app to view the firmware version information
    Affected if Firmware version is not exactly 1.1.39 (this CVE only affects version 1.1.39)
  3. Inspect SD card for vulnerable file
    Remove the Micro SD card from the device and examine its contents for a file named enabled_telnet.dat
    Affected if The enabled_telnet.dat file exists on the SD card and contains telnet configuration data
  4. Check if telnet service is active
    Attempt to connect to the device on telnet port 23 or check running services/processes on the device for telnet-related entries
    Affected if Telnet service is listening on port 23 or running as an active process

You are affected only if you have a Victure PC420 camera running firmware version 1.1.39, with the enabled_telnet.dat file present on its SD card, or with telnet already enabled on the device.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to vendor firmware when available; physically secure the SD card; disable telnet service if possible through device settings; consider network segmentation for affected devices.

Fix this in Pc420 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41612 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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