CVE-2017-11365: Empty passwords validation issue

Published Jul 17, 2017
·
Updated

Certain Symfony products are affected by: Incorrect Access Control. This affects Symfony 2.7.30 and Symfony 2.8.23 and Symfony 3.2.10 and Symfony 3.3.3. The type of exploitation is: remote. The component is: Password validator.

Other sources

CVE-2017-11365: Empty passwords validation issue

Affected Software

31 affected componentsFixes available
composer/symfony/security-core>=2.7.30, <2.7.32, >=2.8.23, <2.8.25, >=3.2.10, <3.2.12, >=3.3.3, <3.3.5
composer/symfony/security>=2.7.30, <2.7.32, >=2.8.23, <2.8.25, >=3.2.10, <3.2.12, >=3.3.3, <3.3.5
composer/symfony/symfony>=2.7.30, <2.7.32, >=2.8.23, <2.8.25, >=3.2.10, <3.2.12, >=3.3.3, <3.3.5
composer/symfony/symfony>=3.3.3<3.3.5
3.3.5
composer/symfony/symfony>=3.2.10<3.2.12
3.2.12
composer/symfony/symfony>=2.8.23<2.8.25
2.8.25
composer/symfony/symfony>=2.7.30<2.7.32
2.7.32
composer/symfony/security>=3.3.3<3.3.5
3.3.5
composer/symfony/security>=3.2.10<3.2.12
3.2.12
composer/symfony/security>=2.8.23<2.8.25
2.8.25
composer/symfony/security>=2.7.30<2.7.32
2.7.32
composer/symfony/security-core>=3.3.3<3.3.5
3.3.5
composer/symfony/security-core>=3.2.10<3.2.12
3.2.12
composer/symfony/security-core>=2.8.23<2.8.25
2.8.25
composer/symfony/security-core>=2.7.30<2.7.32
2.7.32
SensioLabs Symfony=2.7.30
SensioLabs Symfony=2.8.23
SensioLabs Symfony=3.2.10
SensioLabs Symfony=3.3.3
composer/symfony/symfony>=2.7.30, <2.7.32
2.7.32
composer/symfony/symfony>=2.8.23, <2.8.25
2.8.25
composer/symfony/symfony>=3.2.10, <3.2.12
3.2.12
composer/symfony/symfony>=3.3.3, <3.3.5
3.3.5
composer/symfony/security>=2.7.30, <2.7.32
2.7.32
composer/symfony/security>=2.8.23, <2.8.25
2.8.25
composer/symfony/security>=3.2.10, <3.2.12
3.2.12
composer/symfony/security>=3.3.3, <3.3.5
3.3.5
composer/symfony/security-core>=2.7.30, <2.7.32
2.7.32
composer/symfony/security-core>=2.8.23, <2.8.25
2.8.25
composer/symfony/security-core>=3.2.10, <3.2.12
3.2.12
composer/symfony/security-core>=3.3.3, <3.3.5
3.3.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.3.5
  2. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 3.2.12
  3. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.8.25
  4. Upgrade

    Upgrade composer/symfony/symfony to a version that resolves this vulnerability.

    Fixed in 2.7.32
  5. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 3.3.5
  6. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 3.2.12
  7. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.8.25
  8. Upgrade

    Upgrade composer/symfony/security to a version that resolves this vulnerability.

    Fixed in 2.7.32
  9. Upgrade

    Upgrade composer/symfony/security-core to a version that resolves this vulnerability.

    Fixed in 3.3.5
  10. Upgrade

    Upgrade composer/symfony/security-core to a version that resolves this vulnerability.

    Fixed in 3.2.12
  11. Upgrade

    Upgrade composer/symfony/security-core to a version that resolves this vulnerability.

    Fixed in 2.8.25
  12. Upgrade

    Upgrade composer/symfony/security-core to a version that resolves this vulnerability.

    Fixed in 2.7.32

Event History

Jul 17, 2017
Advisory Published
10:54 AM
Data Sourced
via Packagist·10:54 AM
DescriptionSeverityAffected Software
May 23, 2019
CVE Published
via MITRE·05:20 PM
Data Sourced
via MITRE·05:20 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2017-11365?

The severity of CVE-2017-11365 is critical.

2

Which Symfony versions are affected by CVE-2017-11365?

Symfony 2.7.30, Symfony 2.8.23, Symfony 3.2.10, and Symfony 3.3.3 are affected by CVE-2017-11365.

3

What is the type of exploitation for CVE-2017-11365?

The type of exploitation for CVE-2017-11365 is remote.

4

What is the component affected by CVE-2017-11365?

The component affected by CVE-2017-11365 is the Password validator.

5

How can I fix CVE-2017-11365?

To fix CVE-2017-11365, update Symfony to version 2.7.32, 2.8.25, 3.2.12, or 3.3.5.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203