Skip to main navigation Skip to main content Skip to page footer

[Ticket#2009120110000011] Security issues in several third party TYPO3 extensions including cal and direct_mail

1 December 2009 ยท TYPO3 Security Team
Dear users of TYPO3,


Security vulnerabilities have been discovered in following third party TYPO3 
extensions:

"Calendar Base" (cal)
"Direct Mail" (direct_mail)

"[AN] Search it!" (an_searchit)
"Simple download-system with counter and categories" (kk_downloader)
"Automatic Base Tags for RealUrl" (lt_basetag)
"Trips" (mchtrips)
"simple Glossar" (simple_glossar)
"TW Productfinder" (tw_productfinder)
"DB Integration" (wfqbe)




For further information on the issue in extension "Calendar Base" (cal), 
please read the related advisory TYPO3-SA-2009-019 that was published today:

<http: typo3.org teams security security-bulletins typo3-sa-2009-019></http:>


For further information on the issue in extension "Direct 
Mail" (direct_mail), please read the related advisory TYPO3-SA-2009-018 that 
was published today:

<http: typo3.org teams security security-bulletins typo3-sa-2009-018></http:>


For further information on all CSB (Collective Security Bulletin) issues,
please read the related advisory TYPO3-SA-2009-017 that was published today:

<http: typo3.org teams security security-bulletins typo3-sa-2009-017></http:>



In general, the TYPO3 Security Team recommends to read the following pages:

The TYPO3 Security Cookbook:
<http: typo3.org fileadmin security-team typo3_security_cookbook_v-0.5.pdf>

Make sure you are subscribed to the TYPO3 Announce List:
<http: lists.netfielders.de cgi-bin mailman listinfo typo3-announce>

See all TYPO3 security advisories:
<http: typo3.org teams security security-bulletins></http:>


Regards,

Marcus Krause
Member of the TYPO3 Security Team

--
TYPO3 Security Team homepage: <a href="http://typo3.org/teams/security/" target="_blank" rel="noreferrer">http://typo3.org/teams/security/</a>

E-Mail: security@typo3.org

Please note: when replying to this e-mail, please leave the header intact.</http:></http:>