Sensitive data exposure via cleartext memory storage
Published Jul 10, 2025 · Updated Jul 11, 2025
Cleartext storage in Emerson ValveLink products before 14.0 allows local users to access sensitive information from memory. The products retain sensitive data unencrypted in a memory resource that can cross a protection boundary, but Emerson and CISA do not identify the resource, data, or read primitive. Exploitation requires local execution in another control sphere; the published record bounds the effect to confidentiality and integrity, with no service interruption.
Summary
What happened
Cleartext storage in Emerson ValveLink products before 14.0 allows local users to access sensitive information from memory. The products retain sensitive data unencrypted in a memory resource that can cross a protection boundary, but Emerson and CISA do not identify the resource, data, or read primitive. Exploitation requires local execution in another control sphere; the published record bounds the effect to confidentiality and integrity, with no service interruption.
The record
- CVE
- CVE-2025-50109
- Published
- Jul 10, 2025
- Updated
- Jul 11, 2025
- Vendor
- Emerson Electric Co.
- Product
- ValveLink DTM
- Classifications
- CWE-316
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Jul 11, 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=0 <ValveLink 14.0
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