CVE-2019-10910: Check service IDs are valid

Published Apr 16, 2019
·
Updated

CVE-2019-10910: Check service IDs are valid

Other sources

In Symfony before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7, when service ids allow user input, this could allow for SQL Injection and remote code execution. This is related to symfony/dependency-injection.

Affected Software

56 affected componentsFixes available
composer/symfony/dependency-injection>=2.7.0, <2.7.51, >=2.8.0, <2.8.50, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
composer/symfony/proxy-manager-bridge>=2.7.0, <2.7.51, >=2.8.0, <2.8.50, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
composer/symfony/symfony>=2.7.0, <2.7.51, >=2.8.0, <2.8.50, >=3.0.0, <3.1.0, >=3.1.0, <3.2.0, >=3.2.0, <3.3.0, >=3.3.0, <3.4.0, >=3.4.0, <3.4.26, >=4.0.0, <4.1.0, >=4.1.0, <4.1.12, >=4.2.0, <4.2.7
debian/symfony
3.4.22+dfsg-2+deb10u13.4.22+dfsg-2+deb10u24.4.19+dfsg-2+deb11u35.4.23+dfsg-15.4.29+dfsg-15.4.30+dfsg-1
SensioLabs Symfony>=2.7.0<2.7.51
SensioLabs Symfony>=2.8.0<2.8.50
SensioLabs Symfony>=3.4.0<3.4.26
SensioLabs Symfony>=4.1.0<4.1.12
SensioLabs Symfony>=4.2.0<4.2.7
Drupal Drupal>=8.5.0<8.5.15
Drupal Drupal>=8.6.0<8.6.15
composer/symfony/symfony>=4.2.0<4.2.7
4.2.7
composer/symfony/symfony>=4.0.0<4.1.12
4.1.12
composer/symfony/symfony>=3.0.0<3.4.26
3.4.26
composer/symfony/symfony>=2.8.0<2.8.50
2.8.50
composer/symfony/symfony>=2.7.0<2.7.51
2.7.51
composer/symfony/proxy-manager-bridge>=4.2.0<4.2.7
4.2.7
composer/symfony/proxy-manager-bridge>=4.0.0<4.1.12
4.1.12
composer/symfony/proxy-manager-bridge>=3.0.0<3.4.26
3.4.26
composer/symfony/proxy-manager-bridge>=2.8.0<2.8.50
2.8.50
composer/symfony/proxy-manager-bridge>=2.7.0<2.7.51
2.7.51
composer/symfony/dependency-injection>=4.2.0<4.2.7
4.2.7
composer/symfony/dependency-injection>=4.0.0<4.1.12
4.1.12
composer/symfony/dependency-injection>=3.0.0<3.4.26
3.4.26
composer/symfony/dependency-injection>=2.8.0<2.8.50
2.8.50
composer/symfony/dependency-injection>=2.7.0<2.7.51
2.7.51
composer/symfony/symfony>=2.7.0, <2.7.51
2.7.51
composer/symfony/symfony>=2.8.0, <2.8.50
2.8.50
composer/symfony/symfony>=3.0.0, <3.1.0
composer/symfony/symfony>=3.1.0, <3.2.0
composer/symfony/symfony>=3.2.0, <3.3.0
composer/symfony/symfony>=3.3.0, <3.4.0
composer/symfony/symfony>=3.4.0, <3.4.26
3.4.26
composer/symfony/symfony>=4.0.0, <4.1.0
composer/symfony/symfony>=4.1.0, <4.1.12
4.1.12
composer/symfony/symfony>=4.2.0, <4.2.7
4.2.7
composer/symfony/dependency-injection>=2.7.0, <2.7.51
2.7.51
composer/symfony/dependency-injection>=2.8.0, <2.8.50
2.8.50
composer/symfony/dependency-injection>=3.0.0, <3.1.0
composer/symfony/dependency-injection>=3.1.0, <3.2.0
composer/symfony/dependency-injection>=3.2.0, <3.3.0
composer/symfony/dependency-injection>=3.3.0, <3.4.0
composer/symfony/dependency-injection>=3.4.0, <3.4.26
3.4.26
composer/symfony/dependency-injection>=4.0.0, <4.1.0
composer/symfony/dependency-injection>=4.1.0, <4.1.12
4.1.12
composer/symfony/dependency-injection>=4.2.0, <4.2.7
4.2.7
composer/symfony/proxy-manager-bridge>=2.7.0, <2.7.51
2.7.51
composer/symfony/proxy-manager-bridge>=2.8.0, <2.8.50
2.8.50
composer/symfony/proxy-manager-bridge>=3.0.0, <3.1.0
composer/symfony/proxy-manager-bridge>=3.1.0, <3.2.0
composer/symfony/proxy-manager-bridge>=3.2.0, <3.3.0
composer/symfony/proxy-manager-bridge>=3.3.0, <3.4.0
composer/symfony/proxy-manager-bridge>=3.4.0, <3.4.26
3.4.26
composer/symfony/proxy-manager-bridge>=4.0.0, <4.1.0
composer/symfony/proxy-manager-bridge>=4.1.0, <4.1.12
4.1.12
composer/symfony/proxy-manager-bridge>=4.2.0, <4.2.7
4.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3.4.22+dfsg-2+deb10u1Fixed in 3.4.22+dfsg-2+deb10u2Fixed in 4.4.19+dfsg-2+deb11u3Fixed in 5.4.23+dfsg-1Fixed in 5.4.29+dfsg-1Fixed in 5.4.30+dfsg-1
  2. Upgrade

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

    Fixed in 4.2.7
  3. Upgrade

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

    Fixed in 4.1.12
  4. Upgrade

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

    Fixed in 3.4.26
  5. Upgrade

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

    Fixed in 2.8.50
  6. Upgrade

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

    Fixed in 2.7.51
  7. Upgrade

    Upgrade composer/symfony/proxy-manager-bridge to a version that resolves this vulnerability.

    Fixed in 4.2.7
  8. Upgrade

    Upgrade composer/symfony/proxy-manager-bridge to a version that resolves this vulnerability.

    Fixed in 4.1.12
  9. Upgrade

    Upgrade composer/symfony/proxy-manager-bridge to a version that resolves this vulnerability.

    Fixed in 3.4.26
  10. Upgrade

    Upgrade composer/symfony/proxy-manager-bridge to a version that resolves this vulnerability.

    Fixed in 2.8.50
  11. Upgrade

    Upgrade composer/symfony/proxy-manager-bridge to a version that resolves this vulnerability.

    Fixed in 2.7.51
  12. Upgrade

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

    Fixed in 4.2.7
  13. Upgrade

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

    Fixed in 4.1.12
  14. Upgrade

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

    Fixed in 3.4.26
  15. Upgrade

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

    Fixed in 2.8.50
  16. Upgrade

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

    Fixed in 2.7.51

Event History

Apr 16, 2019
Advisory Published
12:48 PM
Data Sourced
via Packagist·12:48 PM
DescriptionSeverityAffected Software
May 16, 2019
CVE Published
via MITRE·09:31 PM
Data Sourced
via MITRE·09:31 PM
Description

Frequently Asked Questions

1

What is CVE-2019-10910?

CVE-2019-10910 is a vulnerability that allows for SQL Injection and remote code execution in Symfony before versions 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7.

2

How severe is CVE-2019-10910?

CVE-2019-10910 is classified as a critical vulnerability with a severity rating of 9.8 out of 10.

3

Which software versions are affected by CVE-2019-10910?

CVE-2019-10910 affects Symfony versions before 2.7.51, 2.8.x before 2.8.50, 3.x before 3.4.26, 4.x before 4.1.12, and 4.2.x before 4.2.7.

4

How can I fix CVE-2019-10910?

To fix CVE-2019-10910, update your Symfony installation to version 2.7.51, 2.8.50, 3.4.26, 4.1.12, or 4.2.7, depending on the version you are using.

5

What is the Common Weakness Enumeration (CWE) of CVE-2019-10910?

The Common Weakness Enumeration (CWE) of CVE-2019-10910 is CWE-89 (SQL Injection).

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