VulnerabilityPublished 28 Aug 2025

CVE-2025-54819: DOS SS1 · Path Traversal

Affects DOS SS1Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 3.0 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 26 Oct 2026.

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 or the CVSS exploit maturity 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

Immediate mitigation should focus on restricting access to the SS1 system to trusted users only and enforcing strong authentication mechanisms to reduce the risk of credential compromise.
Implement strict file system permissions and monitoring to detect unauthorized file modifications, especially in directories managed by SS1.
Employ application-layer controls or web application firewalls (if applicable) to detect and block suspicious path traversal attempts.
Conduct thorough audits of user privileges and remove unnecessary access rights to minimize the pool of potential attackers with authenticated access.
Monitor logs for unusual file overwrite activities or access patterns indicative of exploitation attempts.
Engage with DOS Co., Ltd. for official patches or updates addressing this vulnerability and plan prompt deployment once available.
Consider deploying intrusion detection/prevention systems tailored to detect path traversal or file manipulation attacks within the network segment hosting SS1.
Educate system administrators and users about the risks of path traversal vulnerabilities and the importance of safeguarding credentials.

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, legitimate files may be overwritten by a remote authenticated attacker.

Impact

For European organizations using DOS Co., Ltd.'s SS1 product, this vulnerability poses a significant risk to the integrity of their systems. Since the flaw allows authenticated attackers to overwrite legitimate files, it could lead to unauthorized changes in system configurations, application behavior, or security controls. This may facilitate privilege escalation, persistence, or lateral movement within the network. The impact is particularly critical in environments where SS1 is used for sensitive operations or where file integrity is paramount. Although availability and confidentiality are not directly impacted, the integrity compromise could indirectly affect these aspects if critical system files or security mechanisms are altered. European organizations in sectors such as manufacturing, media, or any industry relying on SS1 for operational processes could face operational disruptions or compliance issues if exploited. The requirement for authentication limits the attack surface but does not eliminate risk, especially if credential compromise or insider threats exist.

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