vulntracker.iovulntracker.io
© 2026 vulntracker.io

CVE-2017-16653

N/A
Published: August 6, 2018 at 09:00 PM UTC
Updated: June 17, 2026 at 01:09 AM UTC
2 products affected across 2 vendorsDebian LinuxSymfony

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Start FreeSign In
Severity
N/A
Exploit prediction
EPSS 1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux· Debiandrupal
95%
9.0
Symfony· Sensiolabsdrupal
95%
2.7.0 ≤ v ≤ 2.7.373.2.0 ≤ v ≤ 3.2.133.3.0 ≤ v ≤ 3.3.123.8.0 ≤ v ≤ 3.8.30

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (3)

x_refsource_CONFIRMIssue TrackingThird Party Advisory
Source: [email protected]
https://github.com/symfony/symfony/pull/24992
x_refsource_CONFIRMIssue TrackingThird Party Advisory
Source: [email protected]
https://symfony.com/blog/cve-2017-16653-csrf-protection-does-not-use-different-tokens-for-http-and-https
Vendor Advisoryx_refsource_DEBIANThird Party Advisory
Source: [email protected]
https://www.debian.org/security/2018/dsa-4262

CVSS

4.3MEDIUM[email protected]
Confidentiality
PARTIAL
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create accountSign in
Free plan, no card