First published: Fri Aug 01 2008(Updated: )
OpenOffice.org (OOo) before 2.1.0 does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update, as demonstrated by evilgrade and DNS cache poisoning.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache OpenOffice | =1.1.5 | |
Apache OpenOffice | =2.0 | |
Apache OpenOffice | =2.0.2 | |
Apache OpenOffice | =2.0.3 | |
Apache OpenOffice | =2.0.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2008-3437 has a moderate severity level due to the potential for arbitrary code execution through malicious updates.
To fix CVE-2008-3437, upgrade to OpenOffice.org version 2.1.0 or later, which includes proper update verification.
CVE-2008-3437 is caused by OpenOffice.org failing to verify the authenticity of updates, allowing man-in-the-middle attacks.
CVE-2008-3437 affects OpenOffice.org versions 1.1.5, 2.0, 2.0.2, 2.0.3, and 2.0.4.
Yes, CVE-2008-3437 can lead to data loss or system compromise if a malicious update is successfully executed.