Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • T TYPO3.CMS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • accessibilityaccessibility
  • TYPO3.CMS
  • Repository
Switch branch/tag
  • TYPO3.CMS
  • typo3
  • sysext
  • backend
  • Classes
  • Controller
  • BackendController.php
Find file BlameHistoryPermalink
  • Christian Kuhn's avatar
    [TASK] unserialize() without objects for extConf · 7e2ce1d2
    Christian Kuhn authored May 27, 2016 and Oliver Hader's avatar Oliver Hader committed May 27, 2016
    To mitigate potential "unsecure unserialize()" issues, the new PHP7
    feature to allow only specific classes or to totally deny object
    creation is rolled out throughout the core in v8.
    
    Since a lot of places use unserialize() and some are critical or
    hard to understand, this is done with a series of patches for
    single areas.
    
    This patch denies object creation at all places where
    $GLOBALS['TYPO3_CONF_VARS']['EXT']['extConf']['anExtension'] is
    unserialized() - the extension manager and ext_conf_template.txt
    handling never handles objects at this place, so it should be
    safe to deny objects at all places.
    
    Change-Id: Ie96e6fb6837418fd765f883b216b7a9c5af5795d
    Resolves: #76320
    Releases: master
    Reviewed-on: https://review.typo3.org/48314
    
    
    Reviewed-by: default avatarMorton Jonuschat <m.jonuschat@mojocode.de>
    Tested-by: default avatarMorton Jonuschat <m.jonuschat@mojocode.de>
    Reviewed-by: Oliver Hader's avatarOliver Hader <oliver.hader@typo3.org>
    Tested-by: Oliver Hader's avatarOliver Hader <oliver.hader@typo3.org>
    7e2ce1d2