An issue was discovered in Symfony before 2.7.38, 2.8.31, 3.2.14, 3.3.13, 3.4-BETA5, and 4.0-BETA5. The current implementation of CSRF protection in Symfony (Version >=2) does not use different tokens for HTTP and HTTPS; therefore the token is subject to MITM attacks on HTTP and can then be used in an HTTPS context to do CSRF attacks.
CVE-2017-16653
This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 1.5%, top 29% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 32(Track)EG Risk 32/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity59% × 45%Exploitation1% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 72%
- KEV
- Not listed
Published
August 6, 2018
Last Modified
November 21, 2024
References (6)
- cve@mitrehttps://github.com/symfony/symfony/pull/24992
- cve@mitrehttps://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- cve@mitrehttps://www.debian.org/security/2018/dsa-4262
- af854a3a-2127-422b-91ae-364da2661108https://github.com/symfony/symfony/pull/24992
- af854a3a-2127-422b-91ae-364da2661108https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
- af854a3a-2127-422b-91ae-364da2661108https://www.debian.org/security/2018/dsa-4262
Affected Packages
(8 across 6 ecosystems)
Packagist(3)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony/security | v3.3.0 ... v3.3.9 (13 versions) | 3.3.13 | — |
| symfony/security-csrf | v3.3.0 ... v3.3.9 (13 versions) | 3.3.13 | — |
| symfony/symfony | v3.3.0 ... v3.3.9 (13 versions) | 3.3.13 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony | — | 3.4.0+dfsg-1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony | — | 3.4.0+dfsg-1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony | — | 3.4.0+dfsg-1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony | — | 3.4.0+dfsg-1 | — |
Debian:9(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| symfony | 2.8.7+dfsg-1.3 | 2.8.7+dfsg-1.3+deb9u1 | — |
Data Freshness Timeline
(refreshed 5× in last 7d / 24× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 127 total refreshes for this CVE.
- 2026-09-07 15:56 UTCEPSS rescore
- 2026-09-04 13:56 UTCEPSS rescore
- 2026-09-04 05:01 UTCEPSS rescore
- 2026-09-02 14:07 UTCEPSS rescore
- 2026-09-01 13:48 UTCEPSS rescore
- 2026-09-01 03:31 UTCEPSS rescore
- 2026-08-31 16:34 UTCOSV refresh
- 2026-08-30 19:13 UTCEPSS rescore
- 2026-08-28 21:36 UTCEPSS rescore
- 2026-08-27 14:20 UTCEPSS rescore
- 2026-08-26 14:41 UTCEPSS rescore
- 2026-08-25 13:44 UTCEPSS rescore
- 2026-08-24 14:10 UTCEPSS rescore
- 2026-08-21 23:44 UTCEPSS rescore
- 2026-08-20 22:50 UTCEPSS rescore
- 2026-08-19 16:59 UTCEPSS rescore
- 2026-08-18 13:43 UTCEPSS rescore
- 2026-08-17 13:42 UTCEPSS rescore
- 2026-08-16 14:51 UTCEPSS rescore
- 2026-08-16 02:10 UTCEPSS rescore
- 2026-08-15 01:26 UTCEPSS rescore
- 2026-08-14 21:24 UTCOSV refresh
- 2026-08-13 21:56 UTCEPSS rescore
- 2026-08-09 13:42 UTCEPSS rescore
- 2026-08-08 16:32 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-06 13:42 UTCEPSS rescore
- 2026-08-05 19:12 UTCEPSS rescore
- 2026-08-04 15:05 UTCEPSS rescore
- 2026-08-04 10:32 UTCEPSS rescore
- 2026-08-03 10:30 UTCEPSS rescore
- 2026-08-02 02:23 UTCEPSS rescore
- 2026-08-01 04:11 UTCEPSS rescore
- 2026-07-30 16:24 UTCEPSS rescore
- 2026-07-30 10:14 UTCOSV refresh
- 2026-07-30 01:26 UTCEPSS rescore
- 2026-07-28 15:32 UTCEPSS rescore
- 2026-07-26 14:51 UTCEPSS rescore
- 2026-07-25 14:13 UTCEPSS rescore
- 2026-07-23 14:15 UTCEPSS rescore
- 2026-07-23 01:28 UTCEG score recompute
- 2026-07-22 22:07 UTCEG score recompute
- 2026-07-22 14:04 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-21 15:21 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-20 17:04 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 14:28 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-19 02:26 UTCEPSS rescore
- 2026-07-18 10:00 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-16 16:59 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 16:54 UTCEPSS rescore
- 2026-07-15 01:56 UTCEPSS rescore
- 2026-07-13 22:26 UTCEPSS rescore
- 2026-07-13 06:09 UTCEPSS rescore
- 2026-07-12 19:08 UTCOSV refresh
- 2026-07-12 05:43 UTCEPSS rescore
- 2026-07-11 08:24 UTCEPSS rescore
- 2026-07-09 19:06 UTCEPSS rescore
- 2026-07-08 15:10 UTCEPSS rescore
- 2026-07-07 13:42 UTCEPSS rescore
- 2026-07-06 16:24 UTCEPSS rescore
- 2026-07-06 02:20 UTCEPSS rescore
- 2026-07-05 02:27 UTCEPSS rescore
- 2026-07-04 06:28 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-07-01 15:02 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-30 23:19 UTCEPSS rescore
- 2026-06-29 14:03 UTCEPSS rescore
- 2026-06-28 14:04 UTCEPSS rescore
- 2026-06-28 04:53 UTCEPSS rescore
- 2026-06-27 03:05 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-25 13:47 UTCEPSS rescore
- 2026-06-24 14:02 UTCEPSS rescore
- 2026-06-24 03:59 UTCOSV refresh
- 2026-06-23 21:30 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-22 14:23 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 14:54 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-21 01:57 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-19 19:23 UTCEPSS rescore
- 2026-06-18 17:50 UTCEPSS rescore
- 2026-06-17 17:50 UTCEPSS rescore
- 2026-06-16 17:50 UTCEPSS rescore
- 2026-06-15 17:45 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-14 23:14 UTCEPSS rescore
- 2026-06-13 22:57 UTCEPSS rescore
- 2026-06-12 23:09 UTCEPSS rescore
- 2026-06-11 13:57 UTCEPSS rescore
- 2026-06-10 22:15 UTCEPSS rescore
Frequently asked(5)
What is CVE-2017-16653?
When was CVE-2017-16653 disclosed?
Is CVE-2017-16653 actively exploited?
What is the CVSS score of CVE-2017-16653?
How do I remediate CVE-2017-16653?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-16653
Is Your Infrastructure Affected by CVE-2017-16653?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.