CVE-2024-50340

CVE-2024-50340 is a medium-severity improper input validation vulnerability in symfony/runtime (composer), affecting versions >= 5.3.0, < 5.4.46. It is fixed in 5.4.46, 6.4.14, 7.1.7.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Symfony allows changing the environment through a query

Description

When the register_argc_argv php directive is set to on , and users call any URL with a special crafted query string, they are able to change the environment or debug mode used by the kernel when handling the request.

Resolution

The SymfonyRuntime now ignores the argv values for non-cli SAPIs PHP runtimes

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

Credits

We would like to thank Vladimir Dusheyko for reporting the issue and Wouter de Jong for providing the fix.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-50340 has a CVSS score of 7.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.4.46, 6.4.14, 7.1.7); upgrading removes the vulnerable code path.

Affected versions

symfony/runtime (>= 5.3.0, < 5.4.46) symfony/runtime (>= 6.0.0, < 6.4.14) symfony/runtime (>= 7.0.0, < 7.1.7) symfony/symfony (>= 5.3.0, < 5.4.46) symfony/symfony (>= 6.0.0, < 6.4.14) symfony/symfony (>= 7.0.0, < 7.1.7)

Security releases

symfony/runtime → 5.4.46 (composer) symfony/runtime → 6.4.14 (composer) symfony/runtime → 7.1.7 (composer) symfony/symfony → 5.4.46 (composer) symfony/symfony → 6.4.14 (composer) symfony/symfony → 7.1.7 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

symfony/runtime to 5.4.46 or later; symfony/runtime to 6.4.14 or later; symfony/runtime to 7.1.7 or later; symfony/symfony to 5.4.46 or later; symfony/symfony to 6.4.14 or later; symfony/symfony to 7.1.7 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2024-50340? CVE-2024-50340 is a medium-severity improper input validation vulnerability in symfony/runtime (composer), affecting versions >= 5.3.0, < 5.4.46. It is fixed in 5.4.46, 6.4.14, 7.1.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
  2. How severe is CVE-2024-50340? CVE-2024-50340 has a CVSS score of 7.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which packages are affected by CVE-2024-50340?
    • symfony/runtime (composer) (versions >= 5.3.0, < 5.4.46)
    • symfony/symfony (composer) (versions >= 5.3.0, < 5.4.46)
  4. Is there a fix for CVE-2024-50340? Yes. CVE-2024-50340 is fixed in 5.4.46, 6.4.14, 7.1.7. Upgrade to this version or later.
  5. Is CVE-2024-50340 exploitable, and should I be worried? Whether CVE-2024-50340 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2024-50340 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2024-50340?
    • Upgrade symfony/runtime to 5.4.46 or later
    • Upgrade symfony/runtime to 6.4.14 or later
    • Upgrade symfony/runtime to 7.1.7 or later
    • Upgrade symfony/symfony to 5.4.46 or later
    • Upgrade symfony/symfony to 6.4.14 or later
    • Upgrade symfony/symfony to 7.1.7 or later

Other vulnerabilities in symfony/runtime

CVE-IDSeverityPackage summary
CVE-2026-47767Mediumsymfony/runtime: SymfonyRuntime CVE-2024-50340 Patch Bypass: Web Requests Can Still Set APP_ENV/APP_DEBUG via parse_str/SAPI Argv Mismatch

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo