CVE-2011-2177: High severity apache openoffice vulnerability

Published May 31, 2011
·
Updated

A new security flaw, potentially allowing execution of arbitrary code with the privileges of the user running the OpenOffice.org suite tools has been reported by the InteVyDis security researchers team: [1] http://intevydis.com/oo0day.html [2] http://twitter.com/#!/legerov/status/75482755194032128

Note: Since no further detailed information is currently available about this flaw, Red Hat Security Response Team is actively investigating the progress done on this (at upstream and reporter side) and will update this record with further information as soon as it is available.

Mitigation: Do not OpenOffice.org documents from untrusted sources.

Other sources

OpenOffice.org v3.3 allows execution of arbitrary code with the privileges of the user running the OpenOffice.org suite tools.

Affected Software

1 affected component
Apache OpenOffice=3.3.0

Event History

May 31, 2011
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverity
Jun 1, 2011
Data Sourced
12:44 PM
Affected Software
Nov 27, 2019
CVE Published
via MITRE·04:42 PM
Data Sourced
via MITRE·04:42 PM
DescriptionWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2011-2177?

CVE-2011-2177 has been classified as a critical vulnerability due to the potential for arbitrary code execution.

2

How do I fix CVE-2011-2177?

To remediate CVE-2011-2177, update to a patched version of Apache OpenOffice beyond 3.3.0.

3

What are the consequences of exploiting CVE-2011-2177?

Exploitation of CVE-2011-2177 could allow attackers to execute arbitrary code with the privileges of the user running the OpenOffice suite.

4

Which software versions are affected by CVE-2011-2177?

CVE-2011-2177 specifically affects Apache OpenOffice version 3.3.0.

5

Is there a workaround for CVE-2011-2177?

There are no official workarounds for CVE-2011-2177; thus, updating the software is the recommended approach.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203