Secondary-system disruption via unauthenticated heartbeat messages
Published May 14, 2024 · Updated Aug 2, 2024
Authentication failure in Siemens SIMATIC RTLS Locating Manager before 3.0.1.1 allows remote attackers to disrupt secondary RTLS systems. The TeeRevProxy service accepts heartbeat messages without properly authenticating their source, allowing forged heartbeats to affect peer availability. Exploitation requires secondary RTLS systems configured through TeeRevProxy and can cause loss of data generated while the attack continues.
Summary
What happened
Authentication failure in Siemens SIMATIC RTLS Locating Manager before 3.0.1.1 allows remote attackers to disrupt secondary RTLS systems. The TeeRevProxy service accepts heartbeat messages without properly authenticating their source, allowing forged heartbeats to affect peer availability. Exploitation requires secondary RTLS systems configured through TeeRevProxy and can cause loss of data generated while the attack continues.
The record
- CVE
- CVE-2024-33494
- Published
- May 14, 2024
- Updated
- Aug 2, 2024
- Vendor
- Siemens
- Product
- SIMATIC RTLS Locating Manager
- Classifications
- CWE-345, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=0 <3.0.1.1
- Affected versionversion=0 <V3.0.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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