Skip to content
OpenAdvisories

Weakness (CWE)

CWE-434: Unrestricted Upload of File with Dangerous Type

Base Draft

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

How to prevent it (8 mitigations)
  1. 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]

  2. 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.

  3. 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]

  4. 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.

  5. 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.

  6. 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]

  7. Implementation

    When running on a web server that supports case-insensitive filenames, perform case-insensitive evaluations of the extensions that are provided.

  8. 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.

Source: MITRE CWE-434

3,441 results · Feed

  • Unscored —

    A CWE-434: Unrestricted Upload of File with Dangerous Type vulnerability exists that could lead to remote code executio…

  • Critical 9.8

    Unrestricted Upload of File with Dangerous Type in Drupal core

    Drupal's JSON:API and REST/File modules allow file uploads through their HTTP APIs. The modules do not correctly run all file validation, which causes an access bypass vulnerability. An attacker might be able to upload files that bypass the file validation pr…

  • Unscored —

    A vulnerability has been identified in COMOS V10.2 (All versions only if web components are used), COMOS V10.3 (All ver…

  • High 8.1

    Unrestricted Upload of File with Dangerous Type in jsdecena/laracom

    Unrestricted Upload of File with Dangerous Type in Packagist jsdecena/laracom prior to v2.0.9.

  • High 7.2
    CVE-2021-44255 Public exploit

    Unrestricted Upload of File with Dangerous Type in motionEye

    Authenticated remote code execution in MotionEye <= 0.42.1 and MotioneEyeOS <= 20200606 allows a remote attacker to upload a configuration backup file containing a malicious python pickle file which will execute arbitrary code on the server.

  • Critical 9.8

    Mingsoft MCMS vulnerable to Remote Code Execution via file upload.

    File upload vulnerability in mingSoft MCMS through 5.2.5, allows remote attackers to execute arbitrary code via a crafted jspx webshell to net.mingsoft.basic.action.web.FileAction#upload.

  • Unscored —

    On BIG-IP ASM & Advanced WAF version 16.1.x before 16.1.2, 15.1.x before 15.1.4.1, 14.1.x before 14.1.4.5, and all vers…

  • Critical 9.8

    Arbitrary file upload in Mingsoft MCMS

    MCMS v5.2.4 was discovered to contain an arbitrary file upload vulnerability via the component /ms/template/writeFileContent.do.

  • Critical 9.8

    Arbitrary File Upload in Mingsoft MCMS

    MCMS v5.2.4 was discovered to have an arbitrary file upload vulnerability in the New Template module, which allows attackers to execute arbitrary code via a crafted ZIP file.

  • Medium 6.6

    Unrestricted Upload of File with Dangerous Type in pimcore/pimcore

    Unrestricted Upload of File with Dangerous Type in Packagist pimcore/pimcore prior to 10.2.7.

  • High 7.2

    Unrestricted Upload of File with Dangerous Type in crater-invoice/crater

    Unrestricted Upload of File with Dangerous Type in GitHub repository crater-invoice/crater prior to 6.0.

  • High 8.8

    This vulnerability allows remote attackers to execute arbitrary code on affected installations of Commvault CommCell 11…

  • High 8.8
    CVE-2021-34995 EPSS 69%

    This vulnerability allows remote attackers to execute arbitrary code on affected installations of Commvault CommCell 11…

  • High 8.8

    Unrestricted Upload of File with Dangerous Type in crater-invoice/crater

    crater is vulnerable to Unrestricted Upload of File with Dangerous Type

  • Unscored —
    CVE-2021-24981 Scanner template

    Directorist – Business Directory Plugin < 7.0.6.2 - CSRF to Remote File Upload

    The Directorist WordPress plugin before 7.0.6.2 was vulnerable to Cross-Site Request Forgery to Remote File Upload leading to arbitrary PHP shell uploads in the wp-content/plugins directory.

  • Critical 9.8

    Chain Sea Information Integration Co., Ltd ai chatbot system - Arbitrary File Upload

    Chain Sea ai chatbot system’s file upload function has insufficient filtering for special characters in URLs, which allows a remote attacker to by-pass file type validation, upload malicious script and execute arbitrary code without authentication, in order t…

  • Critical 9.8

    4MOSAn GCB Doctor - Unrestricted Upload of File

    4MOSAn GCB Doctor’s file upload function has improper user privilege control. A remote attacker can upload arbitrary files including webshell files without authentication and execute arbitrary code in order to perform arbitrary system operations or deny of se…

  • Medium 6.7

    Unrestricted Upload of File with Dangerous Type in unisharp/laravel-filemanager

    This affects versions of the package unisharp/laravel-filemanager before 2.6.2. The upload() function does not sufficiently validate the file type when uploading. An attacker may be able to reproduce the following steps: 1. Install a package with a web Larave…

  • High 7.4
    CVE-2021-43829 EPSS 59%

    Unrestricted Upload of Files in Patrowl

    PatrOwl is a free and open-source solution for orchestrating Security Operations. In versions prior to 1.7.7 PatrowlManager unrestrictly handle upload files in the findings import feature. This vulnerability is capable of uploading dangerous type of file to s…

  • Critical 9.8
    CVE-2021-27860 Exploited EPSS 40%

    Arbitrary file upload vulnerability in FatPipe software

    A vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software prior to versions 10.1.2r60p92 and 10.2.2r44p1 allows a remote, unauthenticated attacker to upload a file to any location on the filesystem. The FatPipe advisory identi…

    KEV Jan 10, 2022
  • Unscored —

    An exposed dangerous function vulnerability exists in Ivanti Avalanche before 6.3.3 allows an attacker with access to t…

  • Medium 4.2

    Arbitrary File Upload

    This affects the package plupload before 2.3.9. A file name containing JavaScript code could be uploaded and run. An attacker would need to trick a user to upload this kind of file.

  • High 7.3

    Missing Upload Filter in TopEase

    Unrestricted File Upload in Web Applications operating on Business-DNA Solutions GmbH’s TopEase® Platform Version <= 7.1.27 in the File Upload Functions allows an authenticated remote attacker with Upload privileges to upload files with any file type, enablin…

  • High 8.8
    CVE-2021-42362 Public exploit EPSS 80%

    WordPress Popular Posts <= 5.3.2 Authenticated Arbitrary File Upload

    The WordPress Popular Posts WordPress plugin is vulnerable to arbitrary file uploads due to insufficient input file type validation found in the ~/src/Image.php file which makes it possible for attackers with contributor level access and above to upload malic…

  • Medium 6.4

    XSS in Talk

    Nextcloud is an open-source, self-hosted productivity platform. The Nextcloud Talk application was vulnerable to a stored Cross-Site Scripting (XSS) vulnerability. For exploitation, a user would need to right-click on a malicious file and open the file in a n…

  • High 8.8

    Grand Vice info Co. webopac7 - Arbitrary File Upload

    Grand Vice info Co. webopac7 file upload function fails to filter special characters. While logging in with general user’s permission, remote attackers can upload malicious script and execute arbitrary code to control the system or interrupt services.

  • High 7.6

    Unrestricted Upload of File with Dangerous Type in bookstackapp/bookstack

    bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type

  • Unscored —

    LearnDash < 2.5.4 - Unauthenticated Arbitrary File Upload

    The LearnDash LMS WordPress plugin before 2.5.4 does not have any authorisation and validation of the file to be uploaded in the learndash_assignment_process_init() function, which could allow unauthenticated users to upload arbitrary files to the web server

  • High 8.0

    Unrestricted Upload of File with Dangerous Type in flatcore/flatcore-cms

    flatcore-cms is vulnerable to Unrestricted Upload of File with Dangerous Type

  • Medium 5.4

    Unrestricted Upload of File with Dangerous Type in bookstackapp/bookstack

    bookstack is vulnerable to Unrestricted Upload of File with Dangerous Type

  • High 8.8

    File Traversal affecting SVG files on Nextcloud Server

    Nextcloud is an open-source, self-hosted productivity platform. Prior to versions 20.0.13, 21.0.5, and 22.2.0, a file traversal vulnerability makes an attacker able to download arbitrary SVG images from the host system, including user provided files. This cou…

  • Medium 6.4

    XSS in Contacts

    Nextcloud is an open-source, self-hosted productivity platform. The Nextcloud Contacts application prior to version 4.0.3 was vulnerable to a stored Cross-Site Scripting (XSS) vulnerability. For exploitation, a user would need to right-click on a malicious fi…

  • Critical 9.8

    Showdoc File Upload Vulnerability

    ShowDoc 2.8.3 ihas a file upload vulnerability, where attackers can use the vulnerability to obtain server permissions.

  • Critical 9.1

    AUVESY Versiondog

    There are multiple API function codes that permit data writing to any file, which may allow an attacker to modify existing files or create new files.

  • High 7.2
    CVE-2021-39352 Public exploit EPSS 56%

    Catch Themes Demo Import <= 1.7 Admin+ Arbitrary File Upload

    The Catch Themes Demo Import WordPress plugin is vulnerable to arbitrary file uploads via the import functionality found in the ~/inc/CatchThemesDemoImport.php file, in versions up to and including 1.7, due to insufficient file type validation. This makes it …

  • Medium 6.3

    Unrestricted Upload of File with Dangerous Type in firefly-iii/firefly-iii

    firefly-iii is vulnerable to Unrestricted Upload of File with Dangerous Type

  • Critical 9.1

    InHand Networks IR615 Router

    InHand Networks IR615 Router's Versions 2.3.0.r4724 and 2.3.0.r4870 do not have a filter or signature check to detect or prevent an upload of malicious files to the server, which may allow an attacker, acting as an administrator, to upload malicious files. Th…

  • High 8.8

    AccessPress Themes - Authenticated Malicious File Upload

    A WordPress plugin and several WordPress themes developed by AccessPress Themes are vulnerable to malicious file uploads via the plugin_offline_installer AJAX action due to a missing capability check in the plugin_offline_installer_callback function found in …

  • Critical 9.8

    Tad TadTools - Arbitrary File Upload

    The file extension of the TadTools file upload function fails to filter, thus remote attackers can upload any types of files and execute arbitrary code without logging in.

  • Critical 9.8

    Integria IMS Remote Code Execution

    Integria IMS in its 5.0.92 version is vulnerable to a Remote Code Execution attack through file uploading. An unauthenticated attacker could abuse the AsyncUpload() function in order to exploit the vulnerability.