GHSA-f35p-hcwf-9f9f CVE-2008-2717

TYPO3 Unrestricted File Upload vulnerability

Medium Packagist

Severity: Medium; The publisher's own rating, not a CVSS score
Exploit chance (EPSS): 3.02%; Chance of exploitation in the next 30 days. Higher than 87.45% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-434 Unrestricted Upload of File with Dangerous Type
Fix: 4.0.9; Upgrade typo3/cms-core to this version or later

Description

TYPO3 4.0.x before 4.0.9, 4.1.x before 4.1.7, and 4.2.x before 4.2.1, uses an insufficiently restrictive default fileDenyPattern for Apache, which allows remote attackers to bypass security restrictions and upload configuration files such as .htaccess, or conduct file upload attacks using multiple extensions.

Affected versions

Packagist

Package	Vulnerable	Fixed in
typo3/cms-core	`>= 4.0.0, < 4.0.9`	`4.0.9`
typo3/cms-core	`>= 4.1.0, < 4.1.7`	`4.1.7`
typo3/cms-core	`>= 4.2.0, < 4.2.1`	`4.2.1`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

typo3/cms-core Packagist → `4.0.9`

composer

composer require typo3/cms-core:^4.0.9

Weakness

CWE-434: Unrestricted Upload of File with Dangerous Type

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.

How to prevent it

Architecture and Design: Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.[REF-422] [REF-423]
Architecture and Design: When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design: Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically. [REF-423]
Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. For example, limiting filenames to alphanumeric characters can help to restrict the introduction of unintended file extensions.
Architecture and Design: Define a very limited set of allowable extensions and only generate filenames that end in these extensions. Consider the possibility of XSS (CWE-79) before allowing .html or .htm file types.
Implementation: Ensure that only one extension is used in the filename. Some web servers, including some versions of Apache, may process files based on inner extensions so that "filename.php.gif" is fed to the PHP interpreter.[REF-422] [REF-423]
Implementation: When running on a web server that supports case-insensitive filenames, perform case-insensitive evaluations of the extensions that are provided.
Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
Implementation: Do not rely exclusively on sanity checks of file contents to ensure that the file is of the expected type and size. It may be possible for an attacker to hide code in some file segments that will still be executed by the server. For example, GIF images may contain a free-form comments field.
Implementation: Do not rely exclusively on the MIME content type or filename attribute when determining how to render a file. Validating the MIME content type and ensuring that it matches the extension is only a partial solution.
Architecture and Design, Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Architecture and Design, Operation: Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2008-2717

Packages

github.com/TYPO3-CMS/core

Timeline

May 1, 2022 Published
Feb 9, 2024 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-68jx-f42c-7599 TYPO3 CMS - Broken Access Control in Backend and Install Tool	High	Also affects typo3/cms-core
GHSA-chm7-4vch-h8vr TYPO3 CMS has Broken Access Control in its Media Module	High	Also affects typo3/cms-core
GHSA-jh32-v29g-68pq TYPO3 CMS has Privilege Escalation & SQL Injection in its Form Framework	High	Also affects typo3/cms-core
GHSA-c78m-c52x-jgwp TYPO3 CMS has Insecure Deserialization via Core API	Medium	Also affects typo3/cms-core
GHSA-jf56-v8jc-jcc5 TYPO3 CMS has Broken Access Control in its File Abstraction Layer	Low	Also affects typo3/cms-core
GHSA-2j54-93q2-3hjq TYPO3 CMS has Broken Access Control in Backend API	Medium	Also affects typo3/cms-core
GHSA-q93m-25xv-94hh TYPO3 CMS: Broken Access Control in Media Module	Medium	Also affects typo3/cms-core
GHSA-qcmw-6rm2-5x78 TYPO3 CMS has Broken Access Control in its DataHandler	Medium	Also affects typo3/cms-core

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor