Subscriber access to diagnostic logs via fetch_log
Published Dec 9, 2024 · Updated Apr 28, 2026
Broken access control in Analytify 5.4.3 and earlier allows remote authenticated users to read diagnostic log data. The 5.5.0 changelog identifies fetch_log as the affected locus, but the public advisory does not disclose the exact authorization check omitted. Subscriber-level access is required, and exposure is limited to sensitive system information contained in the diagnostic log.
Summary
What happened
Broken access control in Analytify 5.4.3 and earlier allows remote authenticated users to read diagnostic log data. The 5.5.0 changelog identifies fetch_log as the affected locus, but the public advisory does not disclose the exact authorization check omitted. Subscriber-level access is required, and exposure is limited to sensitive system information contained in the diagnostic log.
The record
- CVE
- CVE-2024-53814
- Published
- Dec 9, 2024
- Updated
- Apr 28, 2026
- Vendor
- Analytify
- Product
- Analytify
- Classifications
- CWE-497, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 9, 2024CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record 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 <=5.4.3 changes=[{"at":"5.5.0","status":"unaffected"}]
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