# CVE-2024-51996: Symphony has an Authentication Bypass via RememberMe

> Attackers can bypass authentication by exploiting a flaw in Symfony's remember-me cookie validation, allowing unauthorized access to user accounts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-51996, DSA-5813-1, GHSA-cg23-qf8f-62rr, UBUNTU-CVE-2024-51996

## What is CVE-2024-51996?

CVE-2024-51996 is a high-severity authentication bypass vulnerability in symfony, published on 13 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symphony process is a module for the Symphony PHP framework which executes commands in sub-processes. When consuming a persisted remember-me cookie, Symfony does not check if the username persisted in the database matches the username attached with the cookie, leading to authentication bypass. This vulnerability is fixed in 5.4.47, 6.4.15, and 7.1.8.

Weakness: CWE-289 (Authentication Bypass by Alternate Name), CWE-287 (Improper Authentication)

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

6 open source packages ship an affected version, including symfony/security-http.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `symfony/security-http` | Packagist | From 5.3.0 | 5.4.47 |
| `symfony/security-http` | Packagist | From 5.3.0 | 5.4.47 |
| `symfony/security-http` | Packagist | From 6.0.0-BETA1 | 6.4.15 |
| `symfony/security-http` | Packagist | From 6.0.0-BETA1 | 6.4.15 |
| `symfony/security-http` | Packagist | From 7.0.0-BETA1 | 7.1.8 |
| `symfony/security-http` | Packagist | From 7.0.0-BETA1 | 7.1.8 |

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

Upgrade symfony/security-http to a fixed version for your release line: 5.4.47, 6.4.15 or 7.1.8.

## Is CVE-2024-51996 being exploited?

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

Public exploit code:

- CVE-2024-51996 es una vulnerabilidad crítica que afecta al componente security-http del framework Symfony. (github_poc): https://github.com/moften/CVE-2024-51996

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51996 is a high-severity authentication bypass vulnerability in symfony, published on 13 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51996 in the wild and no public exploit code.

Affected packages and fixed versions:
- symfony/security-http (Packagist): affected from 5.3.0; fixed in 5.4.47
- symfony/security-http (Packagist): affected from 5.3.0; fixed in 5.4.47
- symfony/security-http (Packagist): affected from 6.0.0-BETA1; fixed in 6.4.15
- symfony/security-http (Packagist): affected from 6.0.0-BETA1; fixed in 6.4.15
- symfony/security-http (Packagist): affected from 7.0.0-BETA1; fixed in 7.1.8
- symfony/security-http (Packagist): affected from 7.0.0-BETA1; 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-51996/ (Markdown: https://insights.sbomify.com/CVE-2024-51996/index.md)
```

## Sources

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

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