Authenticated file disclosure via logfile path traversal
Published Feb 12, 2025 · Updated Feb 13, 2025
Path traversal in Loggrove's Logfile Update Handler allows remote authenticated users to read files through the logfile parameter. At the affected commit, /read/ uses the supplied path without neutralizing traversal elements or confining the resolved pathname to the log directory. Low-privileged application access is required; exploitation discloses files readable by the Loggrove process, with no reported write or availability impact.
Summary
What happened
Path traversal in Loggrove's Logfile Update Handler allows remote authenticated users to read files through the logfile parameter. At the affected commit, /read/ uses the supplied path without neutralizing traversal elements or confining the resolved pathname to the log directory. Low-privileged application access is required; exploitation discloses files readable by the Loggrove process, with no reported write or availability impact.
The record
- CVE
- CVE-2025-1228
- Published
- Feb 12, 2025
- Updated
- Feb 13, 2025
- Vendor
- Olajowon
- Product
- Loggrove
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 13, 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=e428fac38cc480f011afcb1d8ce6c2bad378ddd6
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
- Gitee issue IBJSXS proof of conceptproof of concept · unverified
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