Credential disclosure via verbose syslog logging
Published Jul 20, 2025 · Updated Jul 22, 2025
Sensitive information exposure in Westermo WeOS 5.24.0 through 5.24.4 allows remote authenticated users to read credentials from logs. The affected logging path writes credentials into syslog files without redaction. Access requires an account authorized to read syslog files, placing credentials handled by verbose logging within that user's reach.
Summary
What happened
Sensitive information exposure in Westermo WeOS 5.24.0 through 5.24.4 allows remote authenticated users to read credentials from logs. The affected logging path writes credentials into syslog files without redaction. Access requires an account authorized to read syslog files, placing credentials handled by verbose logging within that user's reach.
The record
- CVE
- CVE-2025-54319
- Published
- Jul 20, 2025
- Updated
- Jul 22, 2025
- Vendor
- Westermo
- Product
- WeOS
- Classifications
- CWE-532, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 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=5.24.0 <=5.24.4
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