Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2015-4050

Improper Access Control

Published: Jun 02, 2015 | Modified: Dec 31, 2016
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2015-4050
CWEhttps://cwe.mitre.org/data/definitions/284.html

FragmentListener in the HttpKernel component in Symfony 2.3.19 through 2.3.28, 2.4.9 through 2.4.10, 2.5.4 through 2.5.11, and 2.6.0 through 2.6.7, when ESI or SSI support enabled, does not check if the _controller attribute is set, which allows remote attackers to bypass URL signing and security rules by including (1) no hash or (2) an invalid hash in a request to /_fragment.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Symfony Sensiolabs 2.3.19 (including) 2.3.19 (including)
Symfony Sensiolabs 2.3.20 (including) 2.3.20 (including)
Symfony Sensiolabs 2.3.21 (including) 2.3.21 (including)
Symfony Sensiolabs 2.3.22 (including) 2.3.22 (including)
Symfony Sensiolabs 2.3.23 (including) 2.3.23 (including)
Symfony Sensiolabs 2.3.24 (including) 2.3.24 (including)
Symfony Sensiolabs 2.3.25 (including) 2.3.25 (including)
Symfony Sensiolabs 2.3.26 (including) 2.3.26 (including)
Symfony Sensiolabs 2.3.27 (including) 2.3.27 (including)
Symfony Sensiolabs 2.3.28 (including) 2.3.28 (including)
Symfony Sensiolabs 2.4.9 (including) 2.4.9 (including)
Symfony Sensiolabs 2.4.10 (including) 2.4.10 (including)
Symfony Sensiolabs 2.5.4 (including) 2.5.4 (including)
Symfony Sensiolabs 2.5.5 (including) 2.5.5 (including)
Symfony Sensiolabs 2.5.6 (including) 2.5.6 (including)
Symfony Sensiolabs 2.5.7 (including) 2.5.7 (including)
Symfony Sensiolabs 2.5.8 (including) 2.5.8 (including)
Symfony Sensiolabs 2.5.9 (including) 2.5.9 (including)
Symfony Sensiolabs 2.5.10 (including) 2.5.10 (including)
Symfony Sensiolabs 2.5.11 (including) 2.5.11 (including)
Symfony Sensiolabs 2.6.0 (including) 2.6.0 (including)
Symfony Sensiolabs 2.6.1 (including) 2.6.1 (including)
Symfony Sensiolabs 2.6.3 (including) 2.6.3 (including)
Symfony Sensiolabs 2.6.4 (including) 2.6.4 (including)
Symfony Sensiolabs 2.6.5 (including) 2.6.5 (including)
Symfony Sensiolabs 2.6.6 (including) 2.6.6 (including)
Symfony Sensiolabs 2.6.7 (including) 2.6.7 (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use