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

Check your stack
GHSA-g4m9-5hpf-hx72high7.6

Firewall configured with unanimous strategy was not actually unanimous in Symfony

Impact

On Symfony before 4.4.0, when a Firewall checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if all calls to the accessDecisionManager decide to grant access.

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.

Affected rangeRecorded fix
From 4.4.0 before 4.4.7Ecosystem versions4.4.7
From 5.0.0 before 5.0.7Ecosystem versions5.0.7

Version evidence: OSV · GHSA-g4m9-5hpf-hx72

View original version evidence (7 explicit versions)
Affected rangeRecorded fix
From 4.4.0 before 4.4.7Ecosystem versions4.4.7
From 5.0.0 before 5.0.7Ecosystem versions5.0.7

Version evidence: OSV · GHSA-g4m9-5hpf-hx72

View original version evidence (14 explicit versions)
Affected rangeRecorded fix
From 4.4.0 before 4.4.7Ecosystem versions4.4.7
From 5.0.0 before 5.0.7Ecosystem versions5.0.7

Version evidence: OSV · GHSA-g4m9-5hpf-hx72

View original version evidence (14 explicit versions)

Original source description

Description

On Symfony before 4.4.0, when a Firewall checks an access control rule (using the unanimous strategy), it iterates over all rule attributes and grant access only if all calls to the accessDecisionManager decide to grant access.

As of Symfony 4.4.0, a bug was introduced that prevents the check of attributes as soon as accessDecisionManager decide to grant access on one attribute.

Resolution

The accessDecisionManager is now called with all attributes at once, allowing the unanimous strategy being applied on each attribute.

The patch for this issue is available here for the 4.4 branch.

Credits

I would like to thank Antonio J. García Lagar for reporting & Robin Chalas for fixing the issue.

References