Source-code disclosure via case-sensitive extension check
Published Apr 21, 2020 · Updated Aug 4, 2024
Information disclosure in SimpleSAMLphp before 1.18.6 allows remote authenticated users to read module source through uppercase extensions. The module controller in lib/SimpleSAML/Module.php compares the final four path characters to lowercase .php without normalizing case, then serves unmatched files to the browser. Exploitation requires a case-insensitive filesystem, such as Windows, and a request for an existing module PHP file with an uppercase extension.
Summary
What happened
Information disclosure in SimpleSAMLphp before 1.18.6 allows remote authenticated users to read module source through uppercase extensions. The module controller in lib/SimpleSAML/Module.php compares the final four path characters to lowercase .php without normalizing case, then serves unmatched files to the browser. Exploitation requires a case-insensitive filesystem, such as Windows, and a request for an existing module PHP file with an uppercase extension.
The record
- CVE
- CVE-2020-5301
- Published
- Apr 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- SimpleSAMLphp
- Product
- SimpleSAMLphp
- Classifications
- CWE-178, CWE-200, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=< 1.18.6
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