Unauthenticated log disclosure via crafted file parameter
Published Sep 21, 2023 · Updated Sep 24, 2024
Local file inclusion in Frangoteam FUXA 1.1.12 and earlier allows remote attackers to read server log data via a crafted file parameter. The public record identifies file=fuxa.log as the trigger but does not disclose the affected endpoint, code locus, or filename-validation failure. No authentication or user interaction is required, and the documented consequence is limited to confidentiality loss rather than file modification or service interruption.
Summary
What happened
Local file inclusion in Frangoteam FUXA 1.1.12 and earlier allows remote attackers to read server log data via a crafted file parameter. The public record identifies file=fuxa.log as the trigger but does not disclose the affected endpoint, code locus, or filename-validation failure. No authentication or user interaction is required, and the documented consequence is limited to confidentiality loss rather than file modification or service interruption.
The record
- CVE
- CVE-2023-31716
- Published
- Sep 21, 2023
- Updated
- Sep 24, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-98, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2023CVE publishedPublication date reported by the CVE source.
- Sep 24, 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?
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
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