# CVE-2024-50342: Internal address and port enumeration allowed by NoPrivateNetworkHttpClient in symfony/http-client > Attackers can enumerate internal IP addresses and ports via host resolution leaks in the Symfony HTTP client library. - **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Nov 2024 - **Updated:** 7 Nov 2024 - **Also known as:** CLSA-2026-1793214753, DEBIAN-CVE-2024-50342, GHSA-9c3x-r3wp-mgxm, UBUNTU-CVE-2024-50342 ## What is CVE-2024-50342? CVE-2024-50342 is a low-severity vulnerability in symfony, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2024-50342? 12 open source packages ship an affected version, including symfony/http-client and symfony/symfony. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `symfony/http-client` | Packagist | From 4.3.0 | 5.4.47 | | `symfony/http-client` | Packagist | From 4.3.0 | 5.4.47 | | `symfony/http-client` | Packagist | From 6.0.0 | 6.4.15 | | `symfony/http-client` | Packagist | From 6.0.0 | 6.4.15 | | `symfony/http-client` | Packagist | From 7.0.0 | 7.1.8 | | `symfony/http-client` | Packagist | From 7.0.0 | 7.1.8 | | `symfony/symfony` | Packagist | From 4.3.0 | 5.4.47 | | `symfony/symfony` | Packagist | From 4.3.0 | 5.4.47 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.4.15 | | `symfony/symfony` | Packagist | From 6.0.0 | 6.4.15 | | `symfony/symfony` | Packagist | From 7.0.0 | 7.1.8 | | `symfony/symfony` | Packagist | From 7.0.0 | 7.1.8 | Products: Sensiolabs Httpclient. ## How do I fix CVE-2024-50342? Upgrade symfony/http-client to a fixed version for your release line: 5.4.47, 6.4.15 or 7.1.8. ## Is CVE-2024-50342 being exploited? There is no known exploitation of CVE-2024-50342 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-50342 and fix it if it is affected. What it is: CVE-2024-50342 is a low-severity vulnerability in symfony, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-50342 in the wild and no public exploit code. Affected packages and fixed versions: - symfony/http-client (Packagist): affected from 4.3.0; fixed in 5.4.47 - symfony/http-client (Packagist): affected from 4.3.0; fixed in 5.4.47 - symfony/http-client (Packagist): affected from 6.0.0; fixed in 6.4.15 - symfony/http-client (Packagist): affected from 6.0.0; fixed in 6.4.15 - symfony/http-client (Packagist): affected from 7.0.0; fixed in 7.1.8 - symfony/http-client (Packagist): affected from 7.0.0; fixed in 7.1.8 - symfony/symfony (Packagist): affected from 4.3.0; fixed in 5.4.47 - symfony/symfony (Packagist): affected from 4.3.0; fixed in 5.4.47 - symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.15 - symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.15 - symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.1.8 - symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.1.8 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-50342/ (Markdown: https://insights.sbomify.com/CVE-2024-50342/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50342 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50342 - OSV: https://osv.dev/vulnerability/CVE-2024-50342 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-50342/ Summaries are generated and may contain mistakes; the official description above is the record.