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-9c3x-r3wp-mgxmlow3.1

Symfony allows internal address and port enumeration by NoPrivateNetworkHttpClient

Impact

When using the NoPrivateNetworkHttpClient, some internal information is still leaking during host resolution, which leads to possible IP/port enumeration.

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.3.0 before 5.4.47Ecosystem versions5.4.47
From 6.0.0 before 6.4.15Ecosystem versions6.4.15
From 7.0.0 before 7.1.8Ecosystem versions7.1.8

Version evidence: OSV · GHSA-9c3x-r3wp-mgxm

View original version evidence (261 explicit versions)
Affected rangeRecorded fix
From 4.3.0 before 5.4.47Ecosystem versions5.4.47
From 6.0.0 before 6.4.15Ecosystem versions6.4.15
From 7.0.0 before 7.1.8Ecosystem versions7.1.8

Version evidence: OSV · GHSA-9c3x-r3wp-mgxm

View original version evidence (306 explicit versions)

Original source description

Description

When using the NoPrivateNetworkHttpClient, some internal information is still leaking during host resolution, which leads to possible IP/port enumeration.

Resolution

The NoPrivateNetworkHttpClient now filters blocked IPs earlier to prevent such leaks.

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

The second one is available here for branch 5.4 also.

Credits

We would like to thank Linus Karlsson and Chris Smith for reporting the issue and Nicolas Grekas for providing the fix.

References