1826 matches found
By-passing Protection of PharStreamWrapper Interceptor
Insecure deserialization is a vulnerability which occurs when untrusted data is used to abuse the logic of an application. In July 2018, the vulnerability of insecure deserialization when executing Phar archives was addressed by removing the known attack vector in the TYPO3 core. For more details...
GHSA-PPGF-8745-8PGX Insecure Deserialization & Arbitrary Code Execution in TYPO3 CMS
Phar files formerly known as "PHP archives" can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt...
Insecure Deserialization in TYPO3 CMS
It has been discovered that the Form Framework system extension "form" is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package “yaml”, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting...
GHSA-8H28-F46F-M87H Insecure Deserialization in TYPO3 CMS
It has been discovered that the Form Framework system extension "form" is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package “yaml”, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting...
Insecure Deserialization
typo3/cms-core is vulnerable to Insecure Deserialization. The vulnerability is due to request handling that relies on HMAC-SHA1 signing with a sensitive encryption key, which, if exposed, allows attackers to deserialize malicious payloads...
Insecure Deserialization
typo3/cms-form is vulnerable to Insecure Deserialization. The vulnerability is due to the PECL package "yaml" with the PHP setting yml.decodephp enabled, which allows an attacker to deserialize arbitrary YAML to PHP code. An attacker must have a valid backend user account as well yaml.decodephp...
Progress Telerik Report Server Insecure Deserialization (CVE-2024-1800)
The version of Progress Telerik Report Server installed on the remote host is affected by an insecure deserialization vulnerability, as follows: - In Progress Telerik Report Server versions prior to 2024 Q1 10.0.24.130, a remote code execution attack is possible through an insecure deserializatio...
GHSA-5H5V-M596-R6RF TYPO3 Possible Insecure Deserialization in Extbase Request Handling
It has been discovered that request handling in Extbase can be vulnerable to insecure deserialization. User submitted payload has to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionKey as secret - invalid or unsigned payload is not deserialized. However, since sensiti...
TYPO3 Possible Insecure Deserialization in Extbase Request Handling
It has been discovered that request handling in Extbase can be vulnerable to insecure deserialization. User submitted payload has to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionKey as secret - invalid or unsigned payload is not deserialized. However, since sensiti...
GHSA-96JG-PMC4-CX39 TYPO3 CMS Insecure Deserialization
It has been discovered that the Form Framework system extension form is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package yaml, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting...
TYPO3 CMS Insecure Deserialization
It has been discovered that the Form Framework system extension form is vulnerable to Insecure Deserialization when being used with the additional PHP PECL package yaml, which is capable of unserializing YAML contents to PHP objects. A valid backend user account as well as having PHP setting...
TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution
Phar files formerly known as "PHP archives" can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt...
GHSA-CC97-G92W-JM65 TYPO3 CMS Insecure Deserialization & Arbitrary Code Execution
Phar files formerly known as "PHP archives" can act als self extracting archives which leads to the fact that source code is executed when Phar files are invoked. The Phar file format is not limited to be stored with a dedicated file extension - "bundle.phar" would be valid as well as "bundle.txt...
PT-2024-40101 · Typo3 · Typo3
Name of the Vulnerable Software and Affected Versions: TYPO3 affected versions not specified Description: The issue concerns insecure deserialization in Extbase request handling. It requires a user-submitted payload to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionK...
PT-2024-40213 · Unknown +1 · Form Framework +1
Name of the Vulnerable Software and Affected Versions: Form Framework system extension form affected versions not specified Description: The issue concerns Insecure Deserialization in the Form Framework when used with the PHP PECL package yaml. This package can unserialize YAML contents to PHP...
HPESBUX04652 rev.1 - HP-UX 11i v3 Tomcat-based Servlet Engine, Multiple Vulnerabilities
Potential Security Impact: Local: Authentication Bypass, Denial of Service DoS, Disclosure of Information, Unauthorized Access, Insecure Deserialization; Remote: Authentication Bypass, Denial of Service DoS, Disclosure of Information, Unauthorized Access, Insecure Deserialization SUPPORTED SOFTWA...
CVE-2024-4200
In Progress® Telerik® Reporting versions prior to 2024 Q2 18.1.24.2.514, a code execution attack is possible by a local threat actor through an insecure deserialization vulnerability...
CVE-2024-4200
In Progress® Telerik® Reporting versions prior to 2024 Q2 18.1.24.2.514, a code execution attack is possible by a local threat actor through an insecure deserialization vulnerability...