GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
Check your stack
GHSA-jxgr-3v7q-3w9vlow3.1

Symfony's `Security::login` does not take into account custom `user_checker`

Impact

The custom user_checker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login.

Source excerpt · OSV

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

symfony/security-bundle Packagist
Affected rangeRecorded fix
From 6.2.0 before 6.4.10Ecosystem versions6.4.10
From 7.0.0 before 7.0.10Ecosystem versions7.0.10
From 7.1.0 before 7.1.3Ecosystem versions7.1.3

Version evidence: OSV · GHSA-jxgr-3v7q-3w9v

View original version evidence (51 explicit versions)
symfony/symfony Packagist
Affected rangeRecorded fix
From 6.2.0 before 6.4.10Ecosystem versions6.4.10
From 7.0.0 before 7.0.10Ecosystem versions7.0.10
From 7.1.0 before 7.1.3Ecosystem versions7.1.3

Version evidence: OSV · GHSA-jxgr-3v7q-3w9v

View original version evidence (61 explicit versions)

Original source description

Description

The custom user_checker defined on a firewall is not called when Login Programmaticaly with the Security::login method, leading to unwanted login.

Resolution

The Security::login method now ensure to call the configured user_checker.

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

Credits

We would like to thank Oleg Andreyev, Antoine MAKDESSI for reporting the issue and Christian Flothmann for providing the fix.

References