Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


Hello LibreOffice devs,

I just did my first git clone of the core libreoffice codebase, hoping to
poke around to see if I could start helping out with some bugfixing.

After the clone completed, MS Security Essentials popped up with nine
"severe" trojans and exploits. The affected files are .doc, .rtf, and .wmf
-- which would be the places that Windows viruses and trojans would indeed
hide.  I have no way of knowing if these are legit or not, but figured
someone on this list who does Windows dev would want to know.

So, here's the list of files.  Might want to check this out!
Cheers - Billy

\core\svtools\qa\cppunit\data\wmf\fail\CVE-2006-0143-1.wmf
\core\sw\qa\core\data\ww8\pass\CVE-2008-2752-1.doc
\core\sw\qa\core\data\ww8\pass\CVE-2008-2752-2.doc
\core\sw\qa\core\data\ww8\pass\CVE-2008-2752-3.doc
\core\sw\qa\core\data\ww8\pass\CVE-2008-2752-4.doc
\core\sw\qa\core\data\rtf\pass\CVE-2010-3333-1.rtf
\core\writerfilter\qa\cppunittests\rtftok\data\pass\CVE-2010-3333-1.rtf
\core\svtools\qa\cppunit\data\wmf\fail\CVE-2006-0143-2.wmf
\core\sw\qa\core\data\ww8\pass\CVE-2006-6561-1.doc
\core\sw\qa\core\data\ww8\pass\CVE-2006-6628-1.doc
\core\sw\qa\core\data\ww8\fail\CVE-2006-2389-1.doc
\core\sw\qa\core\data\ww8\pass\CVE-2006-3493-1.doc
\core\sw\qa\core\data\ww8\pass\CVE-2007-1347-1.doc
\core\svtools\qa\cppunit\data\emf\fail\CVE-2008-1083-1.emf

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.