Posts by author Ekkehard Gümbel en https://news.typo3.com/article/author/ekkehard-g%C3%BCmbel/blog.author.xml Sat, 25 Jul 2026 03:57:46 +0200 https://news.typo3.com/security/advisory/typo3-20070716-2https://news.typo3.com/security/advisory/typo3-20070716-2#commentsMon, 16 Jul 2007 10:00:00 +0200Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20070716-2An information disclosure issue has been found in the phpmyadmin extension of TYPO3 that may give access to phpinfo() information in special cases. The standalone version of phpmyadmin is not affected. https://news.typo3.com/security/advisory/typo3-security-bulletin-typo3-20070608-1-sql-injection-in-macina-banners-ric-rotationhttps://news.typo3.com/security/advisory/typo3-security-bulletin-typo3-20070608-1-sql-injection-in-macina-banners-ric-rotation#commentsMon, 11 Jun 2007 14:15:00 +0200Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-security-bulletin-typo3-20070608-1-sql-injection-in-macina-banners-ric-rotationIt has been discovered that the extensions macina_banners and its descendant ric_rotation are exposed to an SQL injection issue because they fail to properly sanitize user-supplied input. https://news.typo3.com/security/advisory/security-bulletins-important-security-enhancements-in-typo3-381https://news.typo3.com/security/advisory/security-bulletins-important-security-enhancements-in-typo3-381#commentsMon, 14 Nov 2005 10:17:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/security-bulletins-important-security-enhancements-in-typo3-381Multiple TYPO3 Security Bulletins have been issued, all of which are addressed by the release of TYPO3 3.8.1. https://news.typo3.com/security/advisory/typo3-20051114-7https://news.typo3.com/security/advisory/typo3-20051114-7#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-7Situations are imaginable where sensitive information gets stored in the fileadmin/_temp_/ directory. If misconfigured in your web server, this directory can be browsable and therefore expose that information. https://news.typo3.com/security/advisory/typo3-20051114-3https://news.typo3.com/security/advisory/typo3-20051114-3#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-3Various security issues have been reported for PhpMyAdmin (see www.securityfocus.com/bid/15196 for details.) https://news.typo3.com/security/advisory/typo3-20051114-2https://news.typo3.com/security/advisory/typo3-20051114-2#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-2A Cross Site Scripting issue has been found in showpic.php. https://news.typo3.com/security/advisory/typo3-20051114-6https://news.typo3.com/security/advisory/typo3-20051114-6#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-6 Under special circumstances, setting config.baseURL (see typo3.org/documentation/document-library/doc_core_tsref/quot_CONFIG_quot/ ) to a numeric value ("1") could be used to spoof a malicious baseURL into your TYPO3 cache. It has now been decided to technically prevent this misconfiguration. https://news.typo3.com/security/advisory/typo3-20051114-5https://news.typo3.com/security/advisory/typo3-20051114-5#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-5For convenience, the TYPO3 Install Tool provides a button sets the "encryptionKey" to a random value. It has been observed that only parts of the generated value are actually random. The overall key is therefore unique and -as of today- considered sufficiently secure. However, the effective key length is not the intended one. https://news.typo3.com/security/advisory/typo3-20051114-4https://news.typo3.com/security/advisory/typo3-20051114-4#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-4In the past, a "Shift Reload" from the browser (AKA a GET request with the "no-cache" pragma set) cleared the TYPO3 cache of the requested page. This may be considered a potential target for Denial of Service attacks. https://news.typo3.com/security/advisory/typo3-20051114-1https://news.typo3.com/security/advisory/typo3-20051114-1#commentsMon, 14 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051114-1The file editor functionality in the TYPO3 Install Tool (menu option "Edit files in typo3conf/") has an option that reads "Make backup copy". If set, this will create a backup copy and append a "~" to the original file name. This leads to file names that may be delivered as text files by a web server. Thus, sensitive information (e.g. the content of localconf.php) may be disclosed. https://news.typo3.com/security/advisory/security-bulletins-chc-forum-th-mailformplushttps://news.typo3.com/security/advisory/security-bulletins-chc-forum-th-mailformplus#commentsMon, 07 Nov 2005 15:36:18 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/security-bulletins-chc-forum-th-mailformplusTwo security bulletins regarding the 3rd party extensions "CHC Forum" and "th_mailformplus" have been issued today. Fixed versions are available. https://news.typo3.com/security/advisory/typo3-20051107-2https://news.typo3.com/security/advisory/typo3-20051107-2#commentsMon, 07 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051107-2A weakness in the form validation of th_mailformplus has been discovered that may be abused to inject additional recipients in mail forms. https://news.typo3.com/security/advisory/typo3-20051107-1https://news.typo3.com/security/advisory/typo3-20051107-1#commentsMon, 07 Nov 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20051107-1A bug has been discovered in the "CHC Forum" (chc_forum) extension where some Javascript expressions are not properly caught when entered in forms. Thus, specially crafted entries may be used to inject malicious code. https://news.typo3.com/security/advisory/security-bulletin-typo3-20051010-1-fe-newshttps://news.typo3.com/security/advisory/security-bulletin-typo3-20051010-1-fe-news#commentsMon, 10 Oct 2005 16:24:00 +0200Ekkehard Gümbelhttps://news.typo3.com/security/advisory/security-bulletin-typo3-20051010-1-fe-newsA bug has been discovered in the "Front End News Submitter" (fe_news) where SQL injection is not safely prevented. fe_rtenews is affected as well. https://news.typo3.com/security/advisory/typo3-20050725-1https://news.typo3.com/security/advisory/typo3-20050725-1#commentsMon, 25 Jul 2005 10:00:00 +0200Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20050725-1A debug script exposes system information provided by phpinfo(). By default, the script can be executed by a remote user. https://news.typo3.com/security/advisory/typo3-20050307-1https://news.typo3.com/security/advisory/typo3-20050307-1#commentsMon, 07 Mar 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20050307-1Unless the default encryption key settings have been changed by the administrator, the TYPO3 mailform can be compromised to send mail to a wrong receipient. Thus, spam mails may be sent from a remote site. https://news.typo3.com/security/advisory/typo3-20050304-1https://news.typo3.com/security/advisory/typo3-20050304-1#commentsFri, 04 Mar 2005 10:00:00 +0100Ekkehard Gümbelhttps://news.typo3.com/security/advisory/typo3-20050304-1An issue has been reported where a bug in the "cmw_linklist" extension allows SQL injection attacks. In specific situations, a remote offender can cause malicious database operations.