dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Mar 2023. Known ransomware use
Terramaster Operating SystemOperating system · Terra Master

CVE-2022-24990

HIGH · 7.5 CVSS v3.1 Published 2023-02-07
Fix available
A fix is available. Upgrade to 4.2.31 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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
TerraMaster NAS 4.2.29 and earlier allows remote attackers to discover the administrative password by sending "User-Agent: TNAS" to module/api.php?mobile/webNasIPS and then reading the PWD field in the response.

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 · high confidence

TerraMaster NAS versions 4.2.29 and earlier contain an unauthenticated information disclosure vulnerability in the mobile/webNasIPS API endpoint. Remote attackers can discover the administrator password by sending a request with the specific User-Agent header 'TNAS' to module/api.php?mobile/webNasIPS, which returns the plaintext password in the PWD field of the response.

MitigationUpgrade to a version newer than 4.2.29. If immediate patching is not possible, restrict network access to the administrative interface to trusted IPs only and implement Web Application Firewall rules to block requests with the 'TNAS' User-Agent to this endpoint.

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
Terramaster Operating SystemOperating system
Affected:< 4.2.31

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. Confirm TerraMaster NAS device
    Identify if the target system is a TerraMaster NAS by checking the device model, manufacturer branding, or by making a request to the web interface and examining the HTTP server header or login page for 'TerraMaster' or 'TNAS' references.
    Affected if The system is not a TerraMaster NAS device.
  2. Check Terramaster OS version
    Log into the TerraMaster administrative interface and navigate to 'Control Panel' > 'About' > 'System Information' to view the OS version, or query the API endpoint /module/api.php?mobile/loginCheck for version information.
    Affected if The installed version is lower than 4.2.31 (e.g., 4.2.29, 4.2.30, or any build below 4.2.31).
  3. Verify web API accessibility
    Attempt to reach the API endpoint /module/api.php?mobile/webNasIPS from the network where the NAS is accessible. Use a tool like curl: curl -H 'User-Agent: TNAS' 'http://<target>/module/api.php?mobile/webNasIPS'
    Affected if The endpoint responds with HTTP 200 and returns any JSON data containing a 'PWD' field with a plaintext password.
  4. Check if mobile API module is enabled
    Inspect the TerraMaster web server configuration or PHP module settings to determine if the mobile API module (mobile/webNasIPS) is loaded and accessible.
    Affected if The mobile API module is enabled and the /module/api.php file is executable.
  5. Assess network exposure of administrative interface
    Determine if the TerraMaster web interface (port 80/443) is exposed to untrusted networks by reviewing firewall rules, router port forwarding settings, or VPN/access control configurations.
    Affected if The administrative interface is directly accessible from the internet or untrusted networks without authentication barriers.

A system is affected if it is a TerraMaster NAS running Terramaster OS version lower than 4.2.31 and the /module/api.php?mobile/webNasIPS endpoint is accessible, returning a PWD field in the response when queried with the 'User-Agent: TNAS' header.

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 4.2.31 or later
Fixed in 4.2.31
Interim mitigation

Upgrade to a version newer than 4.2.29. If immediate patching is not possible, restrict network access to the administrative interface to trusted IPs only and implement Web Application Firewall rules to block requests with the 'TNAS' User-Agent to this endpoint.

Recommended fix Moderate confidence

TerraMaster OS version 4.2.31 or later

  1. Log into the TerraMaster NAS administration interface
  2. Navigate to the 'System' or 'Control Panel' settings
  3. Locate the 'System Update' or 'Firmware Update' section
  4. Check for and apply the update to version 4.2.31 or later
  5. After the update completes, verify the system is functioning normally and confirm the vulnerability is no longer present by attempting the described attack vector (with authorization)

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

Fix this in Terramaster Operating System Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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