CVE-2025-49194VulnerabilityPublished 12 Jun 2025

CVE-2025-49194: SICK Media Server · Cleartext Transmission

Affects SICK Media ServerSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

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

CVSS:3.1/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 12 Jun 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

Affected software

Product	Affected	Fixed in
SICK AG SICK Media Server	Affected *	Fixed in–

AI-suggested

1. Immediate network-level mitigation: Deploy network segmentation and isolate the SICK Media Server from untrusted networks. Restrict access to the server to trusted internal networks only. 2. Use encrypted tunnels: Implement VPNs or TLS-based tunnels (e.g., IPsec, SSH tunnels) to secure all communications with the media server until vendor patches are available. 3. Monitor network traffic: Deploy intrusion detection/prevention systems (IDS/IPS) to detect anomalous traffic patterns or unauthorized access attempts targeting the media server. 4. Credential management: Rotate all credentials used by the media server regularly and enforce strong password policies. 5. Vendor engagement: Engage with SICK AG to obtain timelines for patches or updates that address this vulnerability. Request interim guidance or configuration changes to disable insecure authentication methods if possible. 6. Audit and logging: Enable detailed logging on the media server and connected systems to detect suspicious authentication attempts or access patterns. 7. Incident response readiness: Prepare to respond to potential credential compromise incidents by having procedures for account revocation, forensic analysis, and recovery. 8. Avoid use of the affected product in high-risk environments until a secure version is available, or implement compensating controls such as dedicated secure networks and strict access controls.

Description

The server supports authentication methods in which credentials are sent in plaintext over unencrypted channels. If an attacker were to intercept traffic between a client and this server, the credentials would be exposed.

Impact

For European organizations, the impact of this vulnerability can be significant, especially in sectors relying on industrial automation and sensor data management where SICK Media Server is deployed. Exposure of credentials can lead to unauthorized access to critical infrastructure components, potentially allowing attackers to monitor, manipulate, or disrupt industrial processes. This can result in operational downtime, safety risks, intellectual property theft, and regulatory compliance violations (e.g., GDPR if personal data is involved). Since the vulnerability only affects confidentiality and does not directly impact integrity or availability, the immediate risk is credential compromise leading to lateral movement or privilege escalation within the network. However, in industrial contexts, unauthorized access can indirectly cause safety hazards or production interruptions. The lack of encryption also increases the risk in environments where network segmentation or monitoring is insufficient. European organizations with remote or distributed industrial sites connected over untrusted networks (e.g., VPNs, public internet) are particularly vulnerable. Additionally, the absence of user interaction or authentication requirements for exploitation means attackers can passively intercept credentials without alerting users or administrators, increasing the stealth and likelihood of successful attacks.

CWE-319Cleartext Transmission of Sensitive Information (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Architecture and Design
Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols.
Implementation
When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page.
Implementation
When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.
OWASP Cheat Sheets
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.1 (opens in a new tab)
V9.2.2 (opens in a new tab)
V1.9.1 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Harvesting Information via API Event Monitoring (opens in a new tab)
Signature Spoofing by Mixing Signed and Unsigned Content (opens in a new tab)
Sniff Application Code (opens in a new tab)
Interception (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 14:38 UTC

WeaknessesCWE-319

Technical details

References

Community reviews

Related threats