Skip to content
Fencer Intel
medium 6.9

CVE-2010-3689 json

soffice in OpenOffice.org (OOo) 3.x before 3.3 places a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain…

published 2011-01-28 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-3673

cvss
6.9
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 51%
public exploits
0
none known

Summary

soffice in OpenOffice.org (OOo) 3.x before 3.3 places a zero-length directory name in the LD_LIBRARY_PATH, which allows local users to gain privileges via a Trojan horse shared library in the current working directory.

Patch / fix

  • apache openoffice 3.3.0
  • openoffice.org RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-af RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-bg RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-cs RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-da RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-de RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-en RHEL 6 1:3.2.1-19.6.el6_0.5
  • autocorr-es RHEL 6 1:3.2.1-19.6.el6_0.5

red hat advisories RHSA-2011:0183RHSA-2011:0182

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-3689 updated cvss 3.7

OpenOffice.org: soffice insecure LD_LIBRARY_PATH setting

  • Red Hat Enterprise Linux Desktop (v. 5 client) openoffice.org 3.1.1-19.5.el5_5.6, openoffice.org-ure 3.1.1-19.5.el5_5.6, openoffice.org-base 3.1.1-19.5.el5_5.6, openoffice.org-calc 3.1.1-19.5.el5_5.6, openoffice.org-core 3.1.1-19.5.el5_5.6, openoffice.org-draw 3.1.1-19.5.el5_5.6, +10 more
    fixed: vendor fix RHSA-2011:0182
  • Red Hat Enterprise Linux Desktop (v. 6) autocorr-af 3.2.1-19.6.el6_0.5, autocorr-bg 3.2.1-19.6.el6_0.5, autocorr-cs 3.2.1-19.6.el6_0.5, autocorr-da 3.2.1-19.6.el6_0.5, autocorr-de 3.2.1-19.6.el6_0.5, autocorr-en 3.2.1-19.6.el6_0.5, +52 more Red Hat Enterprise Linux Desktop Optional (v. 6) openoffice.org 3.2.1-19.6.el6_0.5, broffice.org-base 3.2.1-19.6.el6_0.5, broffice.org-calc 3.2.1-19.6.el6_0.5, broffice.org-draw 3.2.1-19.6.el6_0.5, broffice.org-math 3.2.1-19.6.el6_0.5, broffice.org-brand 3.2.1-19.6.el6_0.5, +6 more
    fixed: vendor fix RHSA-2011:0183
  • Red Hat Enterprise Linux Desktop Workstation (v. 5 client) openoffice.org 3.1.1-19.5.el5_5.6, openoffice.org-sdk 3.1.1-19.5.el5_5.6 Red Hat Enterprise Linux Optional Productivity Applications (v. 5 server) openoffice.org 3.1.1-19.5.el5_5.6, openoffice.org-sdk 3.1.1-19.5.el5_5.6, openoffice.org-ure 3.1.1-19.5.el5_5.6, openoffice.org-base 3.1.1-19.5.el5_5.6, openoffice.org-calc 3.1.1-19.5.el5_5.6, openoffice.org-core 3.1.1-19.5.el5_5.6, +11 more
    fixed: vendor fix RHSA-2011:0182
  • Red Hat Enterprise Linux Server Optional (v. 6) autocorr-af 3.2.1-19.6.el6_0.5, autocorr-bg 3.2.1-19.6.el6_0.5, autocorr-cs 3.2.1-19.6.el6_0.5, autocorr-da 3.2.1-19.6.el6_0.5, autocorr-de 3.2.1-19.6.el6_0.5, autocorr-en 3.2.1-19.6.el6_0.5, +63 more Red Hat Enterprise Linux Workstation (v. 6) autocorr-af 3.2.1-19.6.el6_0.5, autocorr-bg 3.2.1-19.6.el6_0.5, autocorr-cs 3.2.1-19.6.el6_0.5, autocorr-da 3.2.1-19.6.el6_0.5, autocorr-de 3.2.1-19.6.el6_0.5, autocorr-en 3.2.1-19.6.el6_0.5, +52 more Red Hat Enterprise Linux Workstation Optional (v. 6) openoffice.org 3.2.1-19.6.el6_0.5, broffice.org-base 3.2.1-19.6.el6_0.5, broffice.org-calc 3.2.1-19.6.el6_0.5, broffice.org-draw 3.2.1-19.6.el6_0.5, broffice.org-math 3.2.1-19.6.el6_0.5, broffice.org-brand 3.2.1-19.6.el6_0.5, +6 more
    fixed: vendor fix RHSA-2011:0183
  • Red Hat Enterprise Linux 4 openoffice.org
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.