dbcve.org
Mijia Inkjet Printer FirmwareOperating system · Mi

CVE-2020-10561

CRITICAL · 9.8 CVSS v3.1 Published 2020-06-24
Fix available
A fix is available. Upgrade to 3.4.6_0138 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
An issue was discovered on Xiaomi Mi Jia ink-jet printer < 3.4.6_0138. Injecting parameters to ippserver through the web management background, resulting in command execution vulnerabilities.

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

Command injection vulnerability in the web management interface of Xiaomi Mi Jia ink-jet printer allows attackers to inject parameters into the ippserver component, enabling execution of arbitrary commands. The vulnerability affects versions prior to 3.4.6_0138.

MitigationUpgrade the device firmware to version 3.4.6_0138 or later. If firmware update is unavailable, disable or restrict access to the web management interface to trusted networks only.

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
Mijia Inkjet Printer FirmwareOperating system
Affected:< 3.4.6_0138

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

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

  1. Identify the device model
    Locate your printer and confirm it is a Xiaomi Mi Mijia Inkjet Printer. Check the product label or documentation for the exact model number.
    Affected if Device is not a Mi Mijia Inkjet Printer (not affected by this CVE)
  2. Check the printer firmware version
    Access the Mi Home app, select the printer, go to device settings, and look for firmware/version information. Alternatively, access the printer's web interface (http://<printer-ip>) and check the status or settings page for the firmware version.
    Affected if Firmware version is lower than 3.4.6_0138 (vulnerable)
  3. Verify web management interface accessibility
    Attempt to access the printer's IP address on your local network via HTTP (port 80) or HTTPS (port 443). Also check if port 631 (IPP server) is open and reachable.
    Affected if Web interface is accessible from untrusted networks (exposes the vulnerability to remote attackers)
  4. Check for suspicious network activity
    Monitor network logs or use a network scanner to identify unexpected inbound connections to the printer's web ports (80, 443, 631) from untrusted sources.
    Affected if Unauthorized access attempts to the web management interface are observed (potential exploitation)
  5. Review printer configuration
    If accessible through the web interface, check the ippserver configuration settings or logs for any unexpected commands, scripts, or parameters that were not intentionally configured.
    Affected if Unexpected commands or parameters appear in ippserver logs or configuration (sign of attempted or successful exploitation)

A user is affected if they have a Mi Mijia Inkjet Printer with firmware version below 3.4.6_0138 and the web management interface is accessible, either locally or from untrusted networks.

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
Upgrade available Upgrade to 3.4.6_0138 or later
Fixed in 3.4.6_0138
Interim mitigation

Upgrade the device firmware to version 3.4.6_0138 or later. If firmware update is unavailable, disable or restrict access to the web management interface to trusted networks only.

Recommended fix High confidence

3.4.6_0138 or later

  1. 1. Access the Mijia InkJet Printer web management interface
  2. 2. Navigate to the firmware settings or system update section
  3. 3. Check the current firmware version to confirm it is below 3.4.6_0138
  4. 4. Initiate a firmware update to version 3.4.6_0138 or later
  5. 5. Verify the update was successful by checking the firmware version after rebooting

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

Fix this in Mijia Inkjet Printer Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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