Skip to content
Fencer Intel
medium 5.3

CVE-2015-2309 json

Symfony has unsafe methods in the Request class

published 2y ago modified 2y ago also GHSA-p684-f7fh-jv2j

cvss
5.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

All 2.0.X, 2.1.X, 2.2.X, 2.3.X, 2.4.X, 2.5.X, and 2.6.X versions of the Symfony HttpFoundation component are affected by this security issue.

This issue has been fixed in Symfony 2.3.27, 2.5.11, and 2.6.6. Note that no fixes are provided for Symfony 2.0, 2.1, 2.2, and 2.4 as they are not maintained anymore.

### Description The Symfony\Component\HttpFoundation\Request class provides a mechanism that ensures it does not trust HTTP header values coming from a "non-trusted" client. Unfortunately, it assumes that the remote address is always a trusted client if at least one trusted proxy is involved in the request; this allows a man-in-the-middle attack between the latest trusted proxy and the web server.

The following methods are impacted: getPort(), isSecure(), and getHost(), and getClientIps().

### Resolution All impacted methods now check that the remote address is trusted, which fixes the issue.

The patch for this issue is available [here](https://github.com/symfony/symfony/pull/14166).

Patch / fix

  • packagist symfony/http-foundation 2.3.27, 2.5.11, 2.6.6
  • packagist symfony/symfony 2.3.27, 2.5.11, 2.6.6
  • symfony Debian 14, Debian 13, Debian 12 2.3.21+dfsg-4

debian advisories DEBIAN-CVE-2015-2309

Is CVE-2015-2309 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist symfony/http-foundation
>=2.0.0, <2.3.27
>=2.4.0, <2.5.11
>=2.6.0, <2.6.6
2.3.27
2.5.11
2.6.6
packagist symfony/symfony
>=2.0.0, <2.3.27
>=2.4.0, <2.5.11
>=2.6.0, <2.6.6
2.3.27
2.5.11
2.6.6

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.