Vulnerability in php-league-flysystem (DEBIAN-CVE-2021-32708)

Summary

Vulnerability in php-league-flysystem (DEBIAN-CVE-2021-32708). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.1.3-4 or later.

Original description

The description as published by the source.

Flysystem is an open source file storage library for PHP. The whitespace normalisation using in 1.x and 2.x removes any unicode whitespace. Under certain specific conditions this could potentially allow a malicious user to execute code remotely. The conditions are: A user is allowed to supply the path or filename of an uploaded file, the supplied path or filename is not checked against unicode chars, the supplied pathname checked against an extension deny-list, not an allow-list, the supplied path or filename contains a unicode whitespace char in the extension, the uploaded file is stored in a directory that allows PHP code to be executed. Given these conditions are met a user can upload and execute arbitrary code on the system under attack. The unicode whitespace removal has been replaced with a rejection (exception). For 1.x users, upgrade to 1.1.4. For 2.x users, upgrade to 2.1.1.

Source: OSV.dev (Open Source Vulnerabilities) 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 DEBIAN-CVE-2021-32708 has been found in php-league-flysystem.
Successful exploitation can lead to full system takeover.
What to do: upgrade php-league-flysystem to 1.1.3-4 or later.
If unsure, ask your IT team or search "php-league-flysystem DEBIAN-CVE-2021-32708" on the vendor's site.

DEBIAN-CVE-2021-32708 (php-league-flysystem)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.1.3-4 — 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 (unclassified) exists in php-league-flysystem.

📍 Affected scope

Check the vendor advisory for the affected versions of php-league-flysystem.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.1.3-4.

🛡️ 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 'php-league-flysystem' . 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
Identify exposure identify
```
grep -r 'php-league-flysystem' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で php-league-flysystem を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade php-league-flysystem to 1.1.3-4
```
ステージング環境で 1.1.3-4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Debian:11 php-league-flysystem

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.3-4"}]}]

Debian:12 php-league-flysystem

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.3-4"}]}]

Debian:13 php-league-flysystem

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.3-4"}]}]

Debian:14 php-league-flysystem

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.3-4"}]}]

References

advisory security-tracker.debian.org