Unscored severity · published Dec 31, 2005
CVE-2005-4636
OpenOffice.org 2.0 and earlier, when hyperlinks has been disabled, does not prevent the user from clicking the WWW-browser button in the Hyperlink dialog, which makes it easier…
–
CVSS
0.4%
EPSS
No
On KEV
Description
OpenOffice.org 2.0 and earlier, when hyperlinks has been disabled, does not prevent the user from clicking the WWW-browser button in the Hyperlink dialog, which makes it easier for attackers to trick the user into bypassing intended security settings.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 31% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
OP
Openoffice · Openoffice
1.0.1; 1.0.2; 1.1.0; 1.1.1; 1.1.2; 1.1.3; +3 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2005-4636
CVE.org
https://www.cve.org/CVERecord?id=CVE-2005-4636
qa.openoffice.org
http://qa.openoffice.org/issues/show_bug.cgi?id=53491
Patch
http://securitytracker.com/id?1015419
www.mandriva.com
http://www.mandriva.com/security/advisories?name=MDKSA-2006:033
More from Openoffice
–
CVE-2008-2366
Untrusted search path vulnerability in a certain Red Hat build script for OpenOffice.org (OOo) 1.1.x on Red Hat Enterprise Linux (RHEL) 3 and 4 allows local users to gain…
–
CVE-2007-5745
Multiple heap-based buffer overflows in OpenOffice.org before 2.4 allow remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Quattro Pro…
–
CVE-2007-4575
HSQLDB before 1.8.0.9, as used in OpenOffice.org (OOo) 2 before 2.3.1, allows user-assisted remote attackers to execute arbitrary Java code via crafted database documents, related…
–
CVE-2007-4251
OpenOffice.org (OOo) 2.2 does not properly handle files with multiple extensions, which allows user-assisted remote attackers to cause a denial of service
–
CVE-2007-0245
Heap-based buffer overflow in OpenOffice.org (OOo) 2.2.1 and earlier allows remote attackers to execute arbitrary code via a RTF file with a crafted prtdata tag with a length…