Vulnerability in py3-pillow (ALPINE-CVE-2021-28677)
Summary
Vulnerability in py3-pillow (ALPINE-CVE-2021-28677). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.2.0-r0 or later.
Original description
The description as published by the source.
An issue was discovered in Pillow before 8.2.0. For EPS data, the readline implementation used in EPSImageFile has to deal with any combination of \r and \n as line endings. It used an accidentally quadratic method of accumulating lines while looking for a line ending. A malicious EPS file could use this to perform a DoS of Pillow in the open phase, before an image was accepted for opening.
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 ALPINE-CVE-2021-28677 has been found in py3-pillow.
Risk of unauthorized operations or information disclosure.
What to do: upgrade py3-pillow to 8.2.0-r0 or later.
If unsure, ask your IT team or search "py3-pillow ALPINE-CVE-2021-28677" on the vendor's site.
ALPINE-CVE-2021-28677 (py3-pillow)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.2.0-r0 — 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.
A vulnerability (unclassified) exists in py3-pillow.
Check the vendor advisory for the affected versions of py3-pillow.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.2.0-r0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'py3-pillow' . 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
-
1Identify exposure identify
grep -r 'py3-pillow' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
py3-pillowを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade py3-pillow to 8.2.0-r0ステージング環境で 8.2.0-r0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security.alpinelinux.org