DM2: Improper Limitation of a Pathname to a Restricted Directory
CVE-2025-14224 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in DM2 from Yottamaster, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected DM2 versions: 1.2.0; 1.2.1; 1.2.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.83% chance of exploitation within 30 days, higher than 58% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of DM2 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Yottamaster | DM2 | 1.2.0; 1.2.1; 1.2.2; 1.2.3; 1.2.4; 1.2.5; 1.2.6; 1.2.7; and 29 more ranges | Not stated |
| Yottamaster | DM3 | 1.2.0; 1.2.1; 1.2.2; 1.2.3; 1.2.4; 1.2.5; 1.2.6; 1.2.7; and 29 more ranges | Not stated |
| Yottamaster | DM200 | 1.2.0; 1.2.1; 1.2.2; 1.2.3; 1.2.4; 1.2.5; 1.2.6; 1.2.7; and 29 more ranges | Not stated |
| Yottamaster | Dm2 Firmware | 1.9.12 and earlier | Not stated |
| Yottamaster | Dm3 Firmware | 1.9.12 and earlier | Not stated |
| Yottamaster | Dm200 Firmware | 1.2.23 and earlier | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 2.1 | Low | CNA (vuldb.com) |
| CVSS 3.1 | 4.3 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 9.8 | Critical | NVD |
| CVSS 2.0 | 4.0 | Medium | CNA (vuldb.com) |
Official description
A vulnerability was found in Yottamaster DM2, DM3 and DM200 up to 1.2.23/1.9.12. Affected by this issue is some unknown functionality of the component File Upload. Performing manipulation results in path traversal. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- vuldb.com/?id.334666Third Party Advisory, VDB Entry
- vuldb.com/?submit.701673Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- notion.so/2b76cf4e528a80f6ae50fe21b13ff0b8Exploit, Third Party Advisory
- notion.so/Yottamaster-NAS-Unauth-Operation-2b76cf4e528a80f6ae50fe21b13ff0b8Exploit, Third Party Advisory
Other references
- vuldb.com/?ctiid.334666Permissions Required, VDB Entry
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 9.8 Critical severity
- 8.1 High severity
- 8.1 High severity
- 8.1 High severity
- 7.5 High severity
- 8.8 High severity
Spotted an error? Tell us.