dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2023-34873

HIGH · 8.7 CVSS v4.0 Published 2025-05-23
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
Remotely reachable 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
On MOBOTIX P3 cameras before MX-V4.7.2.18 and Mx6 cameras before MX-V5.2.0.61, the tcpdump feature does not properly validate input, which allows authenticated users to execute code.

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 confidence

MOBOTIX P3 cameras before MX-V4.7.2.18 and Mx6 cameras before MX-V5.2.0.61 contain a command injection vulnerability in the tcpdump feature. The feature does not properly validate user input, allowing authenticated users to execute arbitrary code on the affected devices.

MitigationUpgrade MOBOTIX P3 cameras to MX-V4.7.2.18 or later and Mx6 cameras to MX-V5.2.0.61 or later. If immediate patching is not possible, restrict access to the camera management interface to trusted users only to reduce the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the camera model
    Access the camera management interface or check the device label to confirm whether the device is a MOBOTIX P3 series or Mx6 series camera.
    Affected if The device is a MOBOTIX P3 or Mx6 camera.
  2. Determine the firmware version
    Log into the camera web interface and navigate to the system information or administration section to view the installed firmware version. Alternatively, use the camera's API or CLI if available.
    Affected if The firmware version is below MX-V4.7.2.18 for P3 cameras or below MX-V5.2.0.61 for Mx6 cameras.
  3. Check if the tcpdump feature is accessible
    Navigate to the camera management interface and look for diagnostic or network analysis features. Attempt to locate the tcpdump functionality in the settings or maintenance sections.
    Affected if The tcpdump feature is present and accessible on the device.
  4. Verify authentication status
    Determine whether user authentication is enabled for the camera management interface and check if there are any accounts with access to the tcpdump feature.
    Affected if An authenticated user account exists with access to the tcpdump feature.

The device is affected if it is a MOBOTIX P3 camera with firmware below MX-V4.7.2.18 or an Mx6 camera below MX-V5.2.0.61, and the tcpdump feature is accessible to authenticated users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MOBOTIX P3 cameras to MX-V4.7.2.18 or later and Mx6 cameras to MX-V5.2.0.61 or later. If immediate patching is not possible, restrict access to the camera management interface to trusted users only to reduce the attack surface.

Recommended fix High confidence

MX-V4.7.2.18 or later for P3 cameras; MX-V5.2.0.61 or later for Mx6 cameras

  1. Identify the MOBOTIX camera model (P3 or Mx6 series)
  2. Check the current firmware version via the camera's web interface or admin panel
  3. Download the appropriate fixed firmware from the official MOBOTIX website (www.mobotix.com)
  4. Backup the current camera configuration
  5. Access the camera's admin interface and navigate to the firmware update section
  6. Upload and apply the new firmware version
  7. Verify the firmware upgrade was successful and the camera is functioning normally
  8. Confirm the updated firmware version matches or exceeds MX-V4.7.2.18 for P3 cameras or MX-V5.2.0.61 for Mx6 cameras

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34873 — 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-34873 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