CVE-2016-5091
First published: Mon Jan 23 2017(Updated: )
Extbase in TYPO3 4.3.0 before 6.2.24, 7.x before 7.6.8, and 8.1.1 allows remote attackers to obtain sensitive information or possibly execute arbitrary code via a crafted Extbase action.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| composer/typo3/cms-extbase | =8.1.1 | |
| composer/typo3/cms-extbase | >=7.0<7.6.8 | 7.6.8 |
| composer/typo3/cms-extbase | <6.2.24 | 6.2.24 |
| TYPO3 | <=6.2.23 | |
| TYPO3 | =7.0.0 | |
| TYPO3 | =7.0.2 | |
| TYPO3 | =7.1.0 | |
| TYPO3 | =7.2.0 | |
| TYPO3 | =7.3.0 | |
| TYPO3 | =7.3.1 | |
| TYPO3 | =7.4.0 | |
| TYPO3 | =7.5.0 | |
| TYPO3 | =7.6.0 | |
| TYPO3 | =7.6.1 | |
| TYPO3 | =7.6.2 | |
| TYPO3 | =7.6.3 | |
| TYPO3 | =7.6.4 | |
| TYPO3 | =7.6.5 | |
| TYPO3 | =7.6.6 | |
| TYPO3 | =7.6.7 | |
| TYPO3 | =7.6.8 | |
| TYPO3 | =8.1.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2016-5091
- https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-013/
- http://www.openwall.com/lists/oss-security/2016/05/25/4
- http://www.openwall.com/lists/oss-security/2016/05/26/2
- https://github.com/advisories/GHSA-jxg5-35fj-ccwf (Advisory)
Frequently Asked Questions
What is the severity of CVE-2016-5091?
CVE-2016-5091 has a severity rating of Moderate, due to the potential for sensitive information disclosure and remote code execution.
How do I fix CVE-2016-5091?
To fix CVE-2016-5091, upgrade TYPO3 Extbase to version 6.2.24 or higher, 7.6.8 or higher, or 8.1.1.
Which TYPO3 versions are affected by CVE-2016-5091?
CVE-2016-5091 affects TYPO3 versions prior to 6.2.24, 7.x before 7.6.8, and 8.1.1.
What potential impacts does CVE-2016-5091 have on my system?
CVE-2016-5091 could allow remote attackers to obtain sensitive information or potentially execute arbitrary code.
Is there a workaround for CVE-2016-5091?
There are no known effective workarounds for CVE-2016-5091; upgrading to a patched version is recommended.
- collector/github-advisory
- alias/GHSA-jxg5-35fj-ccwf
- alias/CVE-2016-5091
- collector/github-advisory-latest
- agent/author
- agent/type
- agent/weakness
- agent/references
- agent/severity
- agent/remedy
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/composer
- vendor/typo3
- canonical/typo3 typo3
- version/typo3 typo3/6.2.23
- version/typo3 typo3/7.0.0
- version/typo3 typo3/7.0.2
- version/typo3 typo3/7.1.0
- version/typo3 typo3/7.2.0
- version/typo3 typo3/7.3.0
- version/typo3 typo3/7.3.1
- version/typo3 typo3/7.4.0
- version/typo3 typo3/7.5.0
- version/typo3 typo3/7.6.0
- version/typo3 typo3/7.6.1
- version/typo3 typo3/7.6.2
- version/typo3 typo3/7.6.3
- version/typo3 typo3/7.6.4
- version/typo3 typo3/7.6.5
- version/typo3 typo3/7.6.6
- version/typo3 typo3/7.6.7
- version/typo3 typo3/7.6.8
- version/typo3 typo3/8.1.1