Log injection via unneutralized OCPP logging
Published Mar 12, 2024 · Updated Aug 1, 2024
Log injection in Phoenix Contact CHARX SEC-3xxx firmware 1.5.0 and earlier allows remote attackers to alter a log via OCPP messages. The OCPP logging implementation writes attacker-controlled special characters to a log file without neutralizing them, allowing forged log content. Authentication is not required; the flaw changes log integrity and can contribute to a multi-vulnerability chain that executes code as root.
Summary
What happened
Log injection in Phoenix Contact CHARX SEC-3xxx firmware 1.5.0 and earlier allows remote attackers to alter a log via OCPP messages. The OCPP logging implementation writes attacker-controlled special characters to a log file without neutralizing them, allowing forged log content. Authentication is not required; the flaw changes log integrity and can contribute to a multi-vulnerability chain that executes code as root.
The record
- CVE
- CVE-2024-25997
- Published
- Mar 12, 2024
- Updated
- Aug 1, 2024
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-20
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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 <=1.5.0
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