Skip to content
Fencer Vulns
high 8.8

CVE-2025-62577 json

ETERNUS SF provided by Fsas Technologies Inc.

published 2025-10-20 12 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-35035

cvss
8.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

ETERNUS SF provided by Fsas Technologies Inc. contains an incorrect default permissions vulnerability. A low-privileged user with access to the management server may obtain database credentials, potentially allowing execution of OS commands with administrator privileges.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.0 8.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA 4.0 8.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H
CNA 4.0 8.4 CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected products

  • Fsas Technologies Inc. ETERNUS SF AdvancedCopy Manager Standard Edition (for Solaris 10/ 11)
  • Fsas Technologies Inc. ETERNUS SF Storage Cruiser (for Solaris 10/ 11)
  • Fsas Technologies Inc. ETERNUS SF AdvancedCopy Manager Standard Edition (for RHEL 7/ 8/ 9)
  • Fsas Technologies Inc. ETERNUS SF Expressn (for RHEL 7/ 8/ 9)
  • Fsas Technologies Inc. ETERNUS SF Storage Cruisern (for RHEL 7/ 8/ 9)
  • Fsas Technologies Inc. ETERNUS SF AdvancedCopy Manager Standard Edition (for Windows Server 2016/ 2019/ 2022)
  • Fsas Technologies Inc. ETERNUS SF Express (for Windows Server 2016/ 2019/ 2022)
  • Fsas Technologies Inc. ETERNUS SF Storage Cruiser (for Windows Server 2016/ 2019/ 2022)

Classification

Weakness
  • CWE-276 Incorrect Default Permissions

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.