dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-14187

HIGH · 7.2 CVSS v3.1 Published 2025-12-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
A weakness has been identified in UGREEN DH2100+ up to 5.3.0.251125. This affects the function handler_file_backup_create of the file /v1/file/backup/create of the component nas_svr. Executing a manipulation of the argument path can lead to buffer overflow. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. It is recommended to upgrade the affected component.

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

Buffer overflow vulnerability in the UGREEN DH2100+ NAS device's nas_svr component. The handler_file_backup_create function in the /v1/file/backup_create endpoint does not properly validate the path argument, allowing remote attackers to overflow a buffer and potentially execute arbitrary code.

MitigationUpgrade the UGREEN DH2100+ firmware to a version beyond 5.3.0.251125 that addresses this vulnerability. If no patched version is available, consider network segmentation and restricting access to the affected API endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 UGREEN DH2100+ NAS device
    Locate the device on your network and confirm the model number through the device's web interface (usually at 10.10.10.1 or the IP assigned by your DHCP server), device label, or network inventory records.
    Affected if The device is a UGREEN DH2100+ NAS unit.
  2. Check firmware version
    Log into the NAS web interface, navigate to System Settings > System Update or About section, and record the installed firmware version number.
    Affected if The firmware version is lower than 5.3.0.251125.
  3. Verify nas_svr service is running
    Access the device via SSH or telnet (if enabled), then run 'ps | grep nas_svr' or check the service status to confirm the nas_svr process is active.
    Affected if The nas_svr process is running on the device.
  4. Confirm API endpoint accessibility
    Send a crafted request to the /v1/file/backup_create endpoint using curl or similar tool: curl -X POST http://<device_ip>/v1/file/backup_create -d '{}' and observe the response. Check if authentication is required or if the endpoint is publicly accessible.
    Affected if The /v1/file/backup_create endpoint is accessible without proper authentication or is exposed to untrusted networks.
  5. Inspect for signs of exploitation
    Review system logs in /var/log/ or through the web interface for unusual entries around the backup_create function, unexpected processes, or new user accounts that may indicate attempted or successful exploitation.
    Affected if Unexpected log entries, unauthorized user accounts, or unfamiliar processes are present on the device.

You are affected if you own a UGREEN DH2100+ NAS running firmware version lower than 5.3.0.251125 with the nas_svr service active and the /v1/file/backup_create endpoint 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

Upgrade the UGREEN DH2100+ firmware to a version beyond 5.3.0.251125 that addresses this vulnerability. If no patched version is available, consider network segmentation and restricting access to the affected API endpoint.

Recommended fix Moderate confidence

Latest available firmware version for UGREEN DH2100+ (newer than 5.3.0.251125)

  1. Identify your current UGREEN DH2100+ firmware version in the device settings or administrative interface
  2. Visit the official UGREEN support or download page to check for available firmware updates
  3. Download and install the latest available firmware version for the DH2100+ device
  4. After upgrading, verify that the nas_svr component has been updated and the /v1/file/backup/create endpoint no longer accepts the malicious path manipulation
  5. Confirm the vulnerability is resolved by testing the specific function handler_file_backup_create with various input patterns
Caveat Review release notes for any configuration or feature changes that may require adjustment after firmware upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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