dbcve.org
Espeak NgApplication

CVE-2023-4990

HIGH · 7.5 CVSS v3.1 Published 2023-10-11
Fix available
A fix is available. Upgrade to 1.52.0 / 4.6.0.30210 or later.
See remediation →
84/100
Remediation priority · High
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
Directory traversal vulnerability in MCL-Net versions prior to 4.6 Update Package (P01) may allow attackers to read arbitrary files.

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

Directory traversal vulnerability in MCL-Net versions prior to 4.6 Update Package (P01) allows attackers to manipulate file path requests to read arbitrary files on the server, potentially exposing sensitive system files and configuration data.

MitigationUpgrade MCL-Net to version 4.6 Update Package (P01) or later. Until patched, implement strict input validation on file path parameters and apply least-privilege file system permissions.

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
Espeak NgApplication
Affected:< 1.52.0
Mcl Net FirmwareOperating system
Affected:< 4.6.0.30210

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Check MCL-Net firmware version
    Access the MCL-Net device administrative interface and navigate to System > Status or System > Information to view the firmware version. Alternatively, check the device's about page or firmware file metadata if you have CLI access.
    Affected if The displayed firmware version is lower than 4.6.0.30210 (prior to 4.6 Update Package P01)
  2. Check Espeak Ng version
    If MCL-Net includes an embedded语音 synthesis component, run 'espeak-ng --version' via the system shell or check the software components list in the MCL-Net administrative interface under Software Components or Packages.
    Affected if Espeak Ng version is displayed and is lower than 1.52.0
  3. Identify if file request functionality is exposed
    Review the MCL-Net web interface for features that accept file path inputs, such as file browser, log viewer, backup/restore, or export functions. Check under Configuration > File Management or similar sections.
    Affected if Any web-based feature accepts user-supplied file paths or filenames for reading or viewing
  4. Inspect web server access logs
    Access MCL-Net logs via the administrative interface (typically under Logs > Access Logs or System > Logs) or check server-side log files for requests containing '../' patterns or unusual file path references.
    Affected if Logs show directory traversal patterns like '../' or requests accessing system files outside the intended directory

You are affected if your MCL-Net firmware version is below 4.6.0.30210 (or Espeak Ng is below 1.52.0) AND the file request functionality is exposed or accessible via the web interface.

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 1.52.0 / 4.6.0.30210 or later
Fixed in 1.52.04.6.0.30210
Interim mitigation

Upgrade MCL-Net to version 4.6 Update Package (P01) or later. Until patched, implement strict input validation on file path parameters and apply least-privilege file system permissions.

Recommended fix High confidence

MCL Net Firmware: 4.6.0.30210 (4.6 Update Package P01); Espeak Ng: 1.52.0

  1. 1. Identify the current version of MCL Net Firmware installed on the system
  2. 2. For MCL Net Firmware: If running a version prior to 4.6.0.30210, upgrade to MCL Net Firmware version 4.6.0.30210 (4.6 Update Package P01) or later
  3. 3. Verify the upgrade was successful by checking the firmware version
  4. 4. For Espeak Ng: If the MCL Net product bundles or depends on Espeak Ng, also upgrade to Espeak Ng version 1.52.0 or later
  5. 5. After upgrade, verify that the path traversal vulnerability is resolved by testing file access controls
Caveat Review release notes for MCL Net 4.6 Update Package for any configuration or compatibility changes before upgrading

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

Fix this in Espeak Ng Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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