dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-3705

MEDIUM · 6.8 CVSS v3.1 Published 2025-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
A physical attacker with no privileges can gain full control of the affected device due to improper neutralization of special elements used in an OS Command ('OS Command Injection') when loading a config file from a USB drive.

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

This is an OS Command Injection vulnerability where the device loads configuration files from USB drives without properly sanitizing special characters or elements that could be interpreted as OS commands. A physical attacker with no privileges can place a malicious config file on a USB drive, connect it to the device, and achieve full control of the affected device.

MitigationImplement strict input validation and sanitization for all config file parsing, avoiding use of unsanitized user-supplied data in OS command execution contexts. Consider using allowlist validation or parameterized methods instead of direct command construction.

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
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 checks

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

  1. Identify USB config loading feature
    Review device documentation or system settings to determine if the device supports loading configuration files from USB drives. Look for features named 'USB configuration', 'import config from USB', or similar.
    Affected if The device has a feature to load config files from USB drives and that feature is present in the firmware
  2. Verify if USB config loading is enabled
    Check device settings, web interface, CLI, or configuration menus for options related to USB config import. Determine whether this functionality is currently active or toggleable.
    Affected if USB configuration loading is enabled or available as an option on the device
  3. Inspect config file parsing for input sanitization
    If you have access to firmware or config parsing code, examine how USB-loaded config files are processed. Look for functions that handle config file reading and check if special characters or command sequences are sanitized before use.
    Affected if Config files from USB are parsed without sanitizing shell metacharacters or command injection sequences
  4. Check for OS command execution from USB config data
    Analyze whether parsed configuration values from USB are used in any system(), exec(), or similar command execution functions without validation or parameterization.
    Affected if USB config data flows into OS command execution functions without proper sanitization or safe parameterization
  5. Compare installed firmware version to affected range
    Obtain the device firmware version from system info, boot logs, or about pages. Compare against any published affected version ranges (none provided for this CVE, so treat as potentially affected if USB config feature exists).
    Affected if The firmware version falls within an affected range or the version cannot be determined while the USB config feature is present

The device is affected if it supports loading configuration files from USB drives and that feature is enabled, allowing a physical attacker to inject commands via a malicious config file.

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

Implement strict input validation and sanitization for all config file parsing, avoiding use of unsanitized user-supplied data in OS command execution contexts. Consider using allowlist validation or parameterized methods instead of direct command construction.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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