dbcve.org
En7580 FirmwareOperating system · Mediatek

CVE-2021-31574

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

This is a command injection vulnerability in Config Manager where improper input validation allows an attacker to execute arbitrary commands on the underlying system. A proximal attacker (someone with network proximity) can achieve remote privilege escalation without requiring any user interaction or existing privileges.

MitigationApply vendor patch A20210009 to address the input validation flaw. Until the patch is applied, restrict network access to Config Manager interfaces to trusted proximal 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
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 and firmware version
    Access the device administration interface or use `cat /proc/version` or `uname -a` to determine if the device is a Mediatek En7580 or En7528, then locate the firmware version in the system information or through `cat /etc/version` if available
    Affected if The device is a Mediatek En7580 or En7528 with firmware version below tlm7.3.275.0-82
  2. Verify Config Manager service status
    Check if Config Manager is running on the device, typically through the process list (`ps`) or service status command specific to the firmware
    Affected if Config Manager service is active and listening on network interfaces
  3. Confirm network exposure of Config Manager
    Determine if Config Manager is bound to externally accessible network interfaces or if it is only listening on localhost/internal interfaces
    Affected if Config Manager is bound to WAN or other proximal network interfaces accessible to untrusted attackers
  4. Compare installed firmware against fixed version
    Document the exact firmware version string and compare it numerically or lexically against tlm7.3.275.0-82
    Affected if The installed version is less than tlm7.3.275.0-82 (for example, tlm7.3.275.0-50 or any earlier build)

The environment is affected if the device runs Mediatek En7580 or En7528 firmware versions below tlm7.3.275.0-82 and Config Manager is network-accessible to proximal attackers.

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 vendor patch A20210009 to address the input validation flaw. Until the patch is applied, restrict network access to Config Manager interfaces to trusted proximal networks only.

Recommended fix High confidence

tlm7.3.275.0-82 or later for En7580/En7528 firmware

  1. 1. Identify the specific MediaTek device model (En7580 or En7528) from the affected hardware
  2. 2. Access the device administration interface or CLI to determine the current firmware version
  3. 3. Navigate to MediaTek's official firmware download page (corp.mediatek.com) or the device vendor's support portal
  4. 4. Download the fixed firmware version tlm7.3.275.0-82 or later for your specific device model
  5. 5. Upload and apply the firmware update through the device's web interface or CLI, following the vendor's standard firmware upgrade procedure
  6. 6. After reboot, verify the firmware version has been updated to tlm7.3.275.0-82 or later
  7. 7. Confirm the Config Manager component has been updated to address the command injection vulnerability (CVE-2021-31574)

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
  • 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-2021-31574 — 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-31574 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