CVE-2017-16653

5.9 MEDIUM 1% exploit odds Fix listed

What it is

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.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure.
Exploit odds: 1.5% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2018-08-06 21:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 01:09 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.5% in the next 30 days (EPSS).
Severity: 5.9 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2018-08-06 21:29 UTC
Last modified: 2026-06-17 01:09 UTC
Exploit probability: 1.5% · EPSS, next 30 days
Record status: Modified

Affected

Sensiolabs Symfony ≤ 2.7.37
Sensiolabs Symfony ≤ 3.2.13
Sensiolabs Symfony ≤ 3.3.12
Sensiolabs Symfony ≤ 3.8.30
Debian Linux 9.0

Attack profile CVSS 3.0 · 5.9

Attack vector: Network
Complexity: High
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Raw vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-16653.md and follow it. Check whether this project is affected by CVE-2017-16653. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record