CVE-2025-58072VulnerabilityPublished 28 Aug 2025

CVE-2025-58072: DOS SS1 · Path Traversal

Affects DOS SS1Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

7.5High

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% 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-26.

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

1. Immediate mitigation should include restricting network access to SS1 services on MacOS systems, using firewalls or network segmentation to limit exposure to trusted hosts only. 2. Implement strict monitoring and logging of file access events on affected systems to detect suspicious activity indicative of exploitation attempts. 3. Conduct an inventory of all SS1 installations on MacOS within the organization to identify and prioritize vulnerable instances. 4. Apply vendor patches or updates as soon as they become available; in the absence of patches, consider disabling or isolating the affected functionality if feasible. 5. Employ application-layer controls such as web application firewalls (WAFs) that can detect and block path traversal attack patterns targeting SS1. 6. Educate IT and security teams about this vulnerability and the importance of rapid response to any alerts related to unauthorized file access. 7. Review and tighten file system permissions on MacOS hosts to minimize the amount of sensitive data accessible to the SS1 application process. 8. Consider deploying endpoint detection and response (EDR) solutions capable of identifying anomalous file access behaviors on MacOS systems.

Description

Improper limitation of a pathname to a restricted directory ('Path Traversal') issue exists in SS1 Ver.16.0.0.10 and earlier (Media version:16.0.0a and earlier). If this vulnerability is exploited, arbitrary files may be viewed by a remote unauthenticated attacker.

Impact

For European organizations using DOS Co., Ltd.'s SS1 product on MacOS, this vulnerability poses a significant risk of unauthorized data disclosure. Sensitive corporate data, intellectual property, or personal information could be exposed, leading to compliance violations under GDPR and other data protection regulations. The ability for unauthenticated remote attackers to access arbitrary files increases the risk of espionage, data leaks, and reputational damage. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that rely on SS1 for operations may face elevated risks. The lack of integrity or availability impact limits the threat to confidentiality, but the exposure of sensitive files alone can have severe consequences. Additionally, the MacOS-specific nature means organizations with mixed OS environments must ensure MacOS instances are prioritized for remediation. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future exploitation, especially as proof-of-concept code or exploit tools may emerge.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

Technical details

References

Community reviews

Related threats