Unauthenticated sensitive information disclosure
Published Feb 21, 2025 · Updated Feb 21, 2025
Information disclosure in Loggrove 1.0 allows remote attackers to obtain sensitive information through the read.py component. The published record does not disclose which read.py operation exposes the data or how attacker-controlled input reaches it. The network path requires no privileges or user interaction, and the disclosed consequence is limited to reading sensitive information.
Summary
What happened
Information disclosure in Loggrove 1.0 allows remote attackers to obtain sensitive information through the read.py component. The published record does not disclose which read.py operation exposes the data or how attacker-controlled input reaches it. The network path requires no privileges or user interaction, and the disclosed consequence is limited to reading sensitive information.
The record
- CVE
- CVE-2025-26013
- Published
- Feb 21, 2025
- Updated
- Feb 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-540
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 21, 2025CVE publishedPublication date reported by the CVE source.
- Feb 21, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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 Loggrove arbitrary-file-reading issueproof 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