GHSA-g4g7-q726-v5hg CVE-2018-11406
Symfony CSRF Token Fixation
High
Packagist
- Severity
- 8.8 / 10
- High · CVSS 3.0
- Exploit chance (EPSS)
- 0.75%
- Chance of exploitation in the next 30 days. Higher than 54.94% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
- Available
- 4 packages have a fixed version
Description
An issue was discovered in the Security component in Symfony 2.7.x before 2.7.48, 2.8.x before 2.8.41, 3.3.x before 3.3.17, 3.4.x before 3.4.11, and 4.0.x before 4.0.11. By default, a user's session is invalidated when the user is logged out. This behavior can be disabled through the invalidate_session option. In this case, CSRF tokens were not erased during logout which allowed for CSRF token fixation.
Affected versions
Packagist
| Package | Vulnerable | Fixed in |
|---|---|---|
| symfony/security | >= 2.7.0, < 2.7.48 |
2.7.48 |
| symfony/security | >= 2.8.0, < 2.8.41 |
2.8.41 |
| symfony/security | >= 3.0.0, < 3.3.17 |
3.3.17 |
| symfony/security | >= 3.4.0, < 3.4.11 |
3.4.11 |
| symfony/security | >= 4.0.0, < 4.0.11 |
4.0.11 |
| symfony/security-bundle | >= 2.7.0, < 2.7.48 |
2.7.48 |
| symfony/security-bundle | >= 2.8.0, < 2.8.41 |
2.8.41 |
| symfony/security-bundle | >= 3.0.0, < 3.3.17 |
3.3.17 |
| symfony/security-bundle | >= 3.4.0, < 3.4.11 |
3.4.11 |
| symfony/security-bundle | >= 4.0.0, < 4.0.11 |
4.0.11 |
| symfony/security-http | >= 2.7.0, < 2.7.48 |
2.7.48 |
| symfony/security-http | >= 2.8.0, < 2.8.41 |
2.8.41 |
| symfony/security-http | >= 3.0.0, < 3.3.17 |
3.3.17 |
| symfony/security-http | >= 3.4.0, < 3.4.11 |
3.4.11 |
| symfony/security-http | >= 4.0.0, < 4.0.11 |
4.0.11 |
| symfony/symfony | >= 2.7.0, < 2.7.48 |
2.7.48 |
| symfony/symfony | >= 2.8.0, < 2.8.41 |
2.8.41 |
| symfony/symfony | >= 3.0.0, < 3.3.17 |
3.3.17 |
| symfony/symfony | >= 3.4.0, < 3.4.11 |
3.4.11 |
| symfony/symfony | >= 4.0.0, < 4.0.11 |
4.0.11 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
symfony/security Packagist → 2.7.48
- composer
composer require symfony/security:^2.7.48
symfony/security-bundle Packagist → 2.7.48
- composer
composer require symfony/security-bundle:^2.7.48
symfony/security-http Packagist → 2.7.48
- composer
composer require symfony/security-http:^2.7.48
symfony/symfony Packagist → 2.7.48
- composer
composer require symfony/symfony:^2.7.48
Severity breakdown
CVSS 3.0 8.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: Use the "double-submitted cookie" method as described by Felten and Zeller: When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same. Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult. This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
- github.com/symfony/symfony/commit/319e1bdd43979d9c1559497de8d69adea28ab8d1
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-bundle…
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security-http/C…
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/security/CVE-20…
- github.com/FriendsOfPHP/security-advisories/blob/master/symfony/symfony/CVE-201…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/G4XNB…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UBQK7…
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WU5N2…
- symfony.com/blog/cve-2018-11406-csrf-token-fixation
- symfony.com/cve-2018-11406
- debian.org/security/2018/dsa-4262
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-2v3c-qxhr-7vpv Symfony: Unbounded Recursion in the YAML Inline Lexer Lets a Single Document Crash the Process | High | Also affects symfony/symfony |
| GHSA-r925-mgvr-h9cc Symfony: ReDoS in HeaderUtils::split() Reachable Through the Cache-Control Request Header | High | Also affects symfony/symfony |
| GHSA-h5x3-xfc9-m39h Symfony: UrlGenerator Dot-Segment Encoding Skips Every Other Chained `../` or `./` → Generated URL Collapses Off-Route Under RFC 3986 Normalization | Medium | Also affects symfony/symfony |
| GHSA-v3wm-qf9p-c549 Symfony: HtmlSanitizer URL Parser Deny Gates Underinclusive: Percent-Encoded BiDi Marks and Unicode Whitespace Bypass Visual-Spoofing Defense | Medium | Also affects symfony/symfony |
| GHSA-rrj9-5q2j-4gvr Symfony: Mailomat Mailer Webhook Parser Reads the HMAC Algorithm from the Request: Signature Algorithm Downgrade | Medium | Also affects symfony/symfony |
| GHSA-38cx-cq6f-5755 Symfony: IpUtils::PRIVATE_SUBNETS Omits IPv6 Transition Forms (6to4, NAT64, Teredo, IPv4-compatible): SSRF Bypass in NoPrivateNetworkHttpClient | High | Also affects symfony/symfony |
| GHSA-6h46-9jf5-q59x Symfony: Security Firewall Bypass via failure_forward Subrequest: Unauthenticated Access to access_control-Protected GET Routes | High | Also affects symfony/security-http |
| GHSA-x5qj-865h-mgvm Symfony: HtmlSanitizer UrlAttributeSanitizer Misses URL Attributes | Medium | Also affects symfony/symfony |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor