CVE-2025-58081VulnerabilityPublished 28 Aug 2025

CVE-2025-58081: DOS SS1 · Use of hard-coded password

Affects DOS SS1Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate this vulnerability, European organizations should immediately identify all instances of SS1 running on MacOS and verify the version in use. Upgrading to a patched version once available is the most effective mitigation. In the absence of a patch, organizations should consider the following specific actions: 1) Restrict network access to SS1 instances using firewall rules or network segmentation to limit exposure to untrusted networks. 2) Implement strict monitoring and logging of access to SS1 systems to detect any unauthorized file access attempts. 3) Use host-based intrusion detection systems (HIDS) to alert on suspicious activities related to file access or privilege escalation. 4) Conduct thorough audits of sensitive data stored on affected systems to assess potential exposure. 5) If feasible, replace or isolate MacOS environments running SS1 until a secure version is deployed. 6) Educate IT and security teams about the vulnerability to ensure rapid response to any indicators of compromise. These targeted measures go beyond generic advice by focusing on containment, detection, and minimizing the attack surface specific to this vulnerability.

Description

Use of hard-coded password issue/vulnerability in SS1 Ver.16.0.0.10 and earlier (Media version:16.0.0a and earlier) allows a remote unauthenticated attacker to view arbitrary files with root privileges.

Impact

For European organizations using DOS Co., Ltd.'s SS1 software on MacOS, this vulnerability poses a significant risk to data confidentiality. Attackers exploiting this flaw can access sensitive files with root privileges, potentially exposing intellectual property, personal data, or other critical information. This could lead to regulatory non-compliance issues under GDPR due to unauthorized data disclosure. The lack of required authentication and user interaction means attacks can be automated and launched at scale, increasing the likelihood of compromise. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on SS1 for secure operations may face operational disruptions or reputational damage if sensitive data is leaked. Although integrity and availability are not directly impacted, the confidentiality breach alone can have cascading effects, including loss of customer trust and potential legal liabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Aug 2025, 09:02 UTC

Technical details

References

Community reviews

Related threats