CVE-2024-50342: Internal address and port enumeration allowed by NoPrivateNetworkHttpClient

Published Nov 6, 2024
·
Updated

Description

When using the NoPrivateNetworkHttpClient, some internal information is still leaking during host resolution, which leads to possible IP/port enumeration.

Resolution

The NoPrivateNetworkHttpClient now filters blocked IPs earlier to prevent such leaks.

The fisrt patch for this issue is available here for branch 5.4.

The second one is available here for branch 5.4 also.

Credits

We would like to thank Linus Karlsson and Chris Smith for reporting the issue and Nicolas Grekas for providing the fix.

Other sources

CVE-2024-50342: Internal address and port enumeration allowed by NoPrivateNetworkHttpClient

— Packagist

symfony/http-client is a module for the Symphony PHP framework which provides powerful methods to fetch HTTP resources synchronously or asynchronously. When using the NoPrivateNetworkHttpClient, some internal information is still leaking during host resolution, which leads to possible IP/port enumeration. As of versions 5.4.46, 6.4.14, and 7.1.7 the NoPrivateNetworkHttpClient now filters blocked IPs earlier to prevent such leaks. All users are advised to upgrade. There are no known workarounds for this vulnerability.

— MITRE

Affected Software

39 affected componentsFixes available
composer/symfony/symfony>=7.0.0<7.1.8
7.1.8
composer/symfony/symfony>=6.0.0<6.4.15
6.4.15
composer/symfony/symfony>=4.3.0<5.4.47
5.4.47
composer/symfony/http-client>=7.0.0<7.1.8
7.1.8
composer/symfony/http-client>=6.0.0<6.4.15
6.4.15
composer/symfony/http-client>=4.3.0<5.4.47
5.4.47
SensioLabs Httpclient<5.4.46
SensioLabs Httpclient>=6.0.0<6.4.14
SensioLabs Httpclient>=7.0.0<7.1.7
composer/symfony/symfony>=4.3.0, <4.4.0
composer/symfony/symfony>=4.4.0, <5.0.0
composer/symfony/symfony>=5.0.0, <5.1.0
composer/symfony/symfony>=5.1.0, <5.2.0
composer/symfony/symfony>=5.2.0, <5.3.0
composer/symfony/symfony>=5.3.0, <5.4.0
composer/symfony/symfony>=5.4.0, <5.4.47
5.4.47
composer/symfony/symfony>=6.0.0, <6.1.0
composer/symfony/symfony>=6.1.0, <6.2.0
composer/symfony/symfony>=6.2.0, <6.3.0
composer/symfony/symfony>=6.4.0, <6.4.15
6.4.15
composer/symfony/symfony>=7.0.0, <7.1.0
composer/symfony/symfony>=7.1.0, <7.1.8
7.1.8
composer/symfony/http-client>=4.3.0, <4.4.0
composer/symfony/http-client>=4.4.0, <5.0.0
composer/symfony/http-client>=5.0.0, <5.1.0
composer/symfony/http-client>=5.1.0, <5.2.0
composer/symfony/http-client>=5.2.0, <5.3.0
composer/symfony/http-client>=5.3.0, <5.4.0
composer/symfony/http-client>=5.4.0, <5.4.47
5.4.47
composer/symfony/http-client>=6.0.0, <6.1.0
composer/symfony/http-client>=6.1.0, <6.2.0
composer/symfony/http-client>=6.2.0, <6.3.0
composer/symfony/http-client>=6.4.0, <6.4.15
6.4.15
composer/symfony/http-client>=7.0.0, <7.1.0
composer/symfony/http-client>=7.1.0, <7.1.8
7.1.8
debian/symfony<5.4.23+dfsg-1+deb12u3
5.4.23+dfsg-1+deb12u3
debian/symfony<6.4.15+dfsg-1
6.4.15+dfsg-1
debian/symfony<6.4.15+dfsg-1
6.4.15+dfsg-1
debian/symfony
5.4.53+dfsg-0+deb12u16.4.41+dfsg-0+deb13u16.4.49+dfsg-0+deb13u17.4.23+dfsg-1

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 7.1.8
  2. Upgrade

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

    Fixed in 6.4.15
  3. Upgrade

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

    Fixed in 5.4.47
  4. Upgrade

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

    Fixed in 7.1.8
  5. Upgrade

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

    Fixed in 6.4.15
  6. Upgrade

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

    Fixed in 5.4.47
  7. Upgrade

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

    Fixed in 5.4.23+dfsg-1+deb12u3
  8. Upgrade

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

    Fixed in 6.4.15+dfsg-1
  9. Upgrade

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

    Fixed in 5.4.53+dfsg-0+deb12u1Fixed in 6.4.41+dfsg-0+deb13u1Fixed in 6.4.49+dfsg-0+deb13u1Fixed in 7.4.23+dfsg-1
  10. Upgrade

    Upgrade symfony/http-client to a version that resolves this vulnerability.

    Fixed in 5.4.46
  11. Upgrade

    Upgrade symfony/http-client to a version that resolves this vulnerability.

    Fixed in 6.4.14
  12. Upgrade

    Upgrade symfony/http-client to a version that resolves this vulnerability.

    Fixed in 7.1.7

Event History

Nov 6, 2024
Advisory Published
via GitHub·03:16 PM
CVE Published
via MITRE·09:03 PM
Data Sourced
via MITRE·09:03 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·09:15 PM
DescriptionSeverityAffected Software
Nov 13, 2024
Advisory Published
via Packagist·08:00 AM
Data Sourced
via Packagist·08:00 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2024-50342?

CVE-2024-50342 has been classified as a moderate severity vulnerability due to the potential for IP/port enumeration.

2

How do I fix CVE-2024-50342?

To fix CVE-2024-50342, update your Symfony package to version 7.1.8, 6.4.15, or 5.4.47.

3

What software versions are affected by CVE-2024-50342?

CVE-2024-50342 affects Symfony versions from 5.4.0 to 5.4.46, 6.0.0 to 6.4.14, and 7.0.0 to 7.1.7.

4

What is the cause of CVE-2024-50342?

CVE-2024-50342 arises from improper handling of internal information by the NoPrivateNetworkHttpClient during host resolution.

5

Is there a workaround for CVE-2024-50342?

There is no official workaround for CVE-2024-50342; the recommended action is to upgrade to a patched version.

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