Traffic disclosure and tampering via deprecated TLS
Published Jun 12, 2025 · Updated Jun 17, 2025
Use of a risky TLS protocol in SICK Field Analytics all versions allows remote attackers to read or alter protected network traffic. An undisclosed network service accepts a deprecated TLS protocol instead of restricting negotiation to currently secure versions. No authentication or user interaction is required, but exploitation has high complexity and depends on a session using that protocol; consequences are limited to confidentiality and integrity.
Summary
What happened
Use of a risky TLS protocol in SICK Field Analytics all versions allows remote attackers to read or alter protected network traffic. An undisclosed network service accepts a deprecated TLS protocol instead of restricting negotiation to currently secure versions. No authentication or user interaction is required, but exploitation has high complexity and depends on a session using that protocol; consequences are limited to confidentiality and integrity.
The record
- CVE
- CVE-2025-49196
- Published
- Jun 12, 2025
- Updated
- Jun 17, 2025
- Vendor
- SICK AG
- Product
- SICK Field Analytics
- Classifications
- CWE-327, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 12, 2025CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo