dbcve.org
En7580 FirmwareOperating system · Mediatek

CVE-2021-31575

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In Config Manager, there is a possible command injection due to improper input validation. This could lead to remote escalation of privilege from a proximal attacker with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: A20210009; Issue ID: OSBNB00123234.

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

A command injection vulnerability exists in Config Manager due to improper input validation. An attacker on the proximal network segment can inject malicious commands through unsanitized input fields, achieving remote code execution with elevated privileges without requiring any user interaction.

MitigationApply patch A20210009 immediately. Implement strict input validation and sanitization for all user-supplied data, preferably using allowlists and avoiding shell command execution where possible.

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
En7580 FirmwareOperating system
Affected:< tlm7.3.275.0-82
En7528 FirmwareOperating system
Affected:< tlm7.3.275.0-82

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 device model
    Check the device label, web interface, or CLI output to confirm the hardware model is Mediatek En7580 or En7528
    Affected if Device is not an En7580 or En7528 model
  2. Check installed firmware version
    Access the device's web interface under System/Firmware or use CLI command 'cat /etc/version' or 'fw_printenv' to retrieve the firmware version string
    Affected if Firmware version is lower than tlm7.3.275.0-82 (e.g., tlm7.3.275.0-50, tlm7.3.200.0-10)
  3. Verify Config Manager service status
    Check if the Config Manager web interface is accessible by navigating to the device IP in a browser, or check for Config Manager daemon process via CLI 'ps | grep config' or 'netstat -tlnp | grep 80'
    Affected if Config Manager service is running and accessible on the network
  4. Assess network exposure
    Review firewall rules and network configuration to determine if Config Manager is exposed to untrusted network segments. Check if the management interface is bound to a restricted interface using 'iptables -L' or similar
    Affected if Config Manager is reachable from a network segment beyond the trusted local administrative network

Device is affected if it is an En7580 or En7528 running firmware version below tlm7.3.275.0-82 AND Config Manager is network-accessible.

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

Apply patch A20210009 immediately. Implement strict input validation and sanitization for all user-supplied data, preferably using allowlists and avoiding shell command execution where possible.

Recommended fix High confidence

tlm7.3.275.0-82

  1. 1. Identify all En7580 and En7528 devices in the network inventory
  2. 2. Download the fixed firmware version tlm7.3.275.0-82 from MediaTek's official support portal
  3. 3. Review the firmware upgrade procedure in the device documentation
  4. 4. Apply the firmware upgrade to all affected En7580 and En7528 devices
  5. 5. Verify the firmware version has been successfully applied by checking the device management interface
  6. 6. Confirm the Config Manager service is operational post-upgrade
Caveat Standard firmware upgrade risks apply - ensure backup of configuration and review release notes for any configuration changes

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

Fix this in En7580 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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