CVE-2011-4614 : Detail

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	5.33%	–	–
2022-03-20	–	–	5.33%	–	–
2022-04-03	–	–	5.33%	–	–
2022-05-08	–	–	4.48%	–	–
2022-12-25	–	–	4.48%	–	–
2023-01-01	–	–	4.48%	–	–
2023-02-26	–	–	4.48%	–	–
2023-03-12	–	–	–	7.27%	–
2023-03-19	–	–	–	6.83%	–
2023-05-14	–	–	–	5.09%	–
2023-09-17	–	–	–	5.01%	–
2023-11-19	–	–	–	4.42%	–
2023-12-17	–	–	–	4.42%	–
2024-02-11	–	–	–	7.9%	–
2024-03-17	–	–	–	9.15%	–
2024-03-31	–	–	–	9.15%	–
2024-06-02	–	–	–	13.44%	–
2024-07-28	–	–	–	16.42%	–
2024-09-22	–	–	–	5.75%	–
2024-10-13	–	–	–	5.75%	–
2024-12-22	–	–	–	4.67%	–
2024-12-29	–	–	–	4.67%	–
2025-01-05	–	–	–	4.67%	–
2025-01-19	–	–	–	4.67%	–
2025-03-18	–	–	–	–	5.22%
2025-03-30	–	–	–	–	3.67%
2025-04-06	–	–	–	–	5.22%
2025-04-16	–	–	–	–	3.67%
2025-04-22	–	–	–	–	5.22%
2025-04-22	–	–	–	–	5.22,%

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Date	Percentile
2022-02-06	76%
2022-03-20	77%
2022-04-03	89%
2022-05-08	88%
2022-12-25	89%
2023-01-01	88%
2023-02-26	89%
2023-03-12	93%
2023-03-19	93%
2023-05-14	92%
2023-09-17	92%
2023-11-19	91%
2023-12-17	92%
2024-02-11	94%
2024-03-17	94%
2024-03-31	95%
2024-06-02	96%
2024-07-28	96%
2024-09-22	93%
2024-10-13	94%
2024-12-22	93%
2024-12-29	92%
2025-01-05	93%
2025-01-19	93%
2025-03-18	89%
2025-03-30	87%
2025-04-06	89%
2025-04-16	87%
2025-04-22	89%
2025-04-22	89%

# Exploit Title: Typo3 v4.5-4.7 - Remote Code Execution (RFI/LFI) # Date: 4th January 2012 # Author: MaXe # Software Link: https://typo3.org/download/ # Version: 4.5.0 up to 4.5.8, 4.6.0 and 4.6.1 (+ development releases of 4.7 branch) Typo3 v4.5-4.7 - Remote Code Execution (RFI/LFI) Versions Affected: 4.5.0 up to 4.5.8, 4.6.0 and 4.6.1 (+ development releases of 4.7 branch) Info: TYPO3 is a small to midsize enterprise-class Content Management Framework offering the best of both worlds: out-of-the-box operation with a complete set of standard modules and a clean and sturdy high-performance architecture accomodating virtually every kind of custom solution or extension. External Links: http://typo3.org/ Credits: Björn Pedersen and Christian Toffolo who discovered and reported the issue and the Security Team member Helmut Hummel for providing the patch. (This advisory was rewritten by MaXe @InterN0T to offer a quick overview of the vulnerability, including the removal of all irrelevant and untrue details. -:: The Advisory ::- Requirements for any RCE: - register_globals in the php.ini MUST be enabled (if the exploit fails against a supposed to be vulnerable version, this is why. This setting is often disabled by default.) Requirements for RFI: - allow_url_include has to be enabled (It's often "off" by default.) Proof of Concept: By browsing to a script / page, that uses the following file: typo3/sysext/workspaces/Classes/Controller/AbstractController.php (direct access may not be allowed) It is possible to include PHP code to be executed via the "BACK_PATH" global variable. This can be accessed in ways like: AbstractController.php?BACK_PATH=LFI/RFI%00 The vulnerable piece of code: require_once($GLOBALS['BACK_PATH'] . 'template.php'); Demonstrates, that it is necessary to append a null-byte ( %00 ) after the maliciously crafted input / URL. (Unless your remote file if applicable, is named something.template.php) -:: Solution ::- * Update to the latest version of Typo3 OR change the vulnerable piece of code to: require_once(PATH_site . TYPO3_mainDir . 'template.php'); References: - http://typo3.org/fileadmin/security-team/bug32571/32571.diff - https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2011-004/ - http://news.typo3.org/news/article/important-security-bulletin-pre-announcement-2/