Categories
CVE-2020-5301

Vulnerability in simplesamlphp/simplesamlphp (CVE-2020-5301)

Summary

Vulnerability in simplesamlphp/simplesamlphp (CVE-2020-5301). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.18.6 or later.

Original description

The description as published by the source.

SimpleSAMLphp versions before 1.18.6 contain an information disclosure vulnerability. The module controller in SimpleSAML\Module that processes requests for pages hosted by modules, has code to identify paths ending with .php and process those as PHP code. If no other suitable way of handling the given path exists it presents the file to the browser. The check to identify paths ending with .php does not account for uppercase letters. If someone requests a path ending with e.g. .PHP and the server is serving the code from a case-insensitive file system, such as on Windows, the processing of the PHP code does not occur, and the source code is instead presented to the browser. An attacker may use this issue to gain access to the source code in third-party modules that is meant to be private, or even sensitive. However, the attack surface is considered small, as the attack will only work when SimpleSAMLphp serves such content from a file system that is not case-sensitive, such as on Windows. This issue is fixed in version 1.18.6.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-5301 has been found in simplesamlphp/simplesamlphp.
Risk of unauthorized operations or information disclosure.
What to do: upgrade simplesamlphp/simplesamlphp to 1.18.6 or later.
If unsure, ask your IT team or search "simplesamlphp/simplesamlphp CVE-2020-5301" on the vendor's site.

CVE-2020-5301 (simplesamlphp/simplesamlphp) — CWE-178
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.18.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-178) exists in simplesamlphp/simplesamlphp.

📍 Affected scope

Check the vendor advisory for the affected versions of simplesamlphp/simplesamlphp.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.18.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'simplesamlphp/simplesamlphp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'simplesamlphp/simplesamlphp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で simplesamlphp/simplesamlphp を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade simplesamlphp/simplesamlphp to 1.18.6

    ステージング環境で 1.18.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist simplesamlphp/simplesamlphp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details