Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-15094

Vulnerability in symfony/http-kernel (CVE-2020-15094)

Summary

Vulnerability in symfony/http-kernel (CVE-2020-15094). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.1.5 or later.

Original description

The description as published by the source.

In Symfony before versions 4.4.13 and 5.1.5, the CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible. This has been fixed in versions 4.4.13 and 5.1.5.

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-15094 has been found in symfony/http-kernel.
Successful exploitation can lead to full system takeover.
What to do: upgrade symfony/http-kernel to 5.1.5 or later.
If unsure, ask your IT team or search "symfony/http-kernel CVE-2020-15094" on the vendor's site.

CVE-2020-15094 (symfony/http-kernel) — CWE-212
Attack vector: remote (network-reachable) / no user interaction
Patched: 5.1.5 — 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-212) exists in symfony/http-kernel.

📍 Affected scope

Check the vendor advisory for the affected versions of symfony/http-kernel.

🔥 Severity

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

🔧 How to fix

Update to 5.1.5.

🛡️ 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 'symfony/http-kernel' . 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 'symfony/http-kernel' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade symfony/http-kernel to 5.1.5

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

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

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

Affected packages

Packagist symfony/http-kernel
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.1.5"}]}]
Packagist symfony/symfony
[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.1.5"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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