# CVE-2024-50343: Incorrect response from Validator when input ends with `\n` in symfony/validator

> Attackers can bypass regex validation rules ending with $ by appending newlines, requiring specific validator configuration.

- **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:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-50343, GHSA-g3rh-rrhp-jhh9, UBUNTU-CVE-2024-50343

## What is CVE-2024-50343?

CVE-2024-50343 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/validator is a module for the Symphony PHP framework which provides tools to validate values. It is possible to trick a `Validator` configured with a regular expression using the `$` metacharacters, with an input ending with `\n`. Symfony as of versions 5.4.43, 6.4.11, and 7.1.4 now uses the `D` regex modifier to match the entire input. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-50343?

12 open source packages ship an affected version, including symfony/symfony and symfony/validator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/symfony` | Packagist | All versions | 5.4.43 |
| `symfony/symfony` | Packagist | All versions | 5.4.43 |
| `symfony/symfony` | Packagist | From 6.0.0 | 6.4.11 |
| `symfony/symfony` | Packagist | From 6.0.0 | 6.4.11 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.1.4 |
| `symfony/symfony` | Packagist | From 7.0.0 | 7.1.4 |
| `symfony/validator` | Packagist | All versions | 5.4.43 |
| `symfony/validator` | Packagist | All versions | 5.4.43 |
| `symfony/validator` | Packagist | From 6.0.0 | 6.4.11 |
| `symfony/validator` | Packagist | From 6.0.0 | 6.4.11 |
| `symfony/validator` | Packagist | From 7.0.0 | 7.1.4 |
| `symfony/validator` | Packagist | From 7.0.0 | 7.1.4 |

## How do I fix CVE-2024-50343?

Upgrade symfony/symfony to a fixed version for your release line: 5.4.43, 6.4.11 or 7.1.4.

## Is CVE-2024-50343 being exploited?

There is no known exploitation of CVE-2024-50343 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50343 and fix it if it is affected.

What it is: CVE-2024-50343 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-50343 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/symfony (Packagist): affected all versions; fixed in 5.4.43
- symfony/symfony (Packagist): affected all versions; fixed in 5.4.43
- symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.11
- symfony/symfony (Packagist): affected from 6.0.0; fixed in 6.4.11
- symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.1.4
- symfony/symfony (Packagist): affected from 7.0.0; fixed in 7.1.4
- symfony/validator (Packagist): affected all versions; fixed in 5.4.43
- symfony/validator (Packagist): affected all versions; fixed in 5.4.43
- symfony/validator (Packagist): affected from 6.0.0; fixed in 6.4.11
- symfony/validator (Packagist): affected from 6.0.0; fixed in 6.4.11
- symfony/validator (Packagist): affected from 7.0.0; fixed in 7.1.4
- symfony/validator (Packagist): affected from 7.0.0; fixed in 7.1.4

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-50343/ (Markdown: https://insights.sbomify.com/CVE-2024-50343/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50343
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50343
- OSV: https://osv.dev/vulnerability/CVE-2024-50343

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50343/
Summaries are generated and may contain mistakes; the official description above is the record.