File Station EUVD-2025-17338

The CVSS 7.5 (High) score reflects significant availability impact but must be contextualized: (1) The AV:N/AC:L/PR:N/UI:N characteristics indicate network-accessible, low-complexity exploitation without privilege escalation or user interaction—this is favorable for attackers; (2) However, authentication is required (implicit in 'gains a user account'), which reduces real-world exploitability compared to unauthenticated DoS; (3) The vulnerability is confidentiality-neutral (C:N/I:N) and only affects availability (A:H), making it a pure DoS vector; (4) No KEV/CISA active exploitation data, POC, or EPSS score is provided, suggesting either recent disclosure or low real-world traction; (5) Per SSVC framework: exploitability is probable (low complexity), technical impact is complete service outage (availability), but requires prior authentication—this elevates required user risk tolerance but reduces environmental risk. Real-world priority is MEDIUM-HIGH for organizations running unpatched File Station 5 with untrusted user populations, but LOW-MEDIUM if access is restricted to trusted administrators.

An internal user or compromised account holder (e.g., via credential theft or insider threat) authenticates to the NAS and accesses File Station 5 via the web interface. The attacker then crafts a malicious request to a vulnerable endpoint—possibly targeting file operations, directory listing, or metadata retrieval—containing crafted parameters that trigger a code path with insufficient NULL pointer validation. This causes the application to dereference a null pointer, raising an unhandled exception that crashes the File Station 5 process. The NAS remains online but File Station 5 becomes unavailable, disrupting legitimate file access and backup operations. Recovery requires manual service restart or automatic restart via monitoring. No privilege escalation or data breach occurs, but availability impact is immediate and disruptive. Attack complexity is low; a proof-of-concept could be developed with fuzzing or code analysis once the vulnerable code path is identified.