What is the severity of CVE-2017-9432?

CVE-2017-9432 has a critical severity level due to its potential for stack-based buffer overflow leading to out-of-bounds write.

How do I fix CVE-2017-9432?

To mitigate CVE-2017-9432, update libstaroffice to version 0.0.4 or later that addresses the vulnerability.

What type of vulnerability is CVE-2017-9432?

CVE-2017-9432 is classified as a buffer overflow vulnerability affecting the DatabaseName::read function.

What versions are affected by CVE-2017-9432?

CVE-2017-9432 affects libstaroffice versions prior to 0.0.4.

Who is impacted by CVE-2017-9432?

Users and organizations that utilize vulnerable versions of libstaroffice for document processing are at risk due to CVE-2017-9432.

Vulnerability/
CVE-2017-9432

critical

9.8

CWE

787 119

5/6/2017

12/6/2017

CVE-2017-9432: Buffer Overflow

First published: Mon Jun 05 2017(Updated: )

Document Liberation Project libstaroffice before 2017-04-07 has an out-of-bounds write caused by a stack-based buffer overflow related to the DatabaseName::read function in lib/StarWriterStruct.cxx.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Libstaroffice	<=0.0.3

Remedy

https://github.com/fosnola/libstaroffice/commit/2d6253c7a692a3d92785dd990fce7256ea05e794

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-9432?
CVE-2017-9432 has a critical severity level due to its potential for stack-based buffer overflow leading to out-of-bounds write.
How do I fix CVE-2017-9432?
To mitigate CVE-2017-9432, update libstaroffice to version 0.0.4 or later that addresses the vulnerability.
What type of vulnerability is CVE-2017-9432?
CVE-2017-9432 is classified as a buffer overflow vulnerability affecting the DatabaseName::read function.
What versions are affected by CVE-2017-9432?
CVE-2017-9432 affects libstaroffice versions prior to 0.0.4.
Who is impacted by CVE-2017-9432?
Users and organizations that utilize vulnerable versions of libstaroffice for document processing are at risk due to CVE-2017-9432.

agent/references
agent/type
agent/first-publish-date
agent/last-modified-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/severity
agent/weakness
agent/remedy
agent/author
agent/softwarecombine
agent/description
agent/tags
agent/event
vendor/libstaroffice project
canonical/libstaroffice
version/libstaroffice/0.0.3

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2017-9432?
CVE-2017-9432 has a critical severity level due to its potential for stack-based buffer overflow leading to out-of-bounds write.
How do I fix CVE-2017-9432?
To mitigate CVE-2017-9432, update libstaroffice to version 0.0.4 or later that addresses the vulnerability.
What type of vulnerability is CVE-2017-9432?
CVE-2017-9432 is classified as a buffer overflow vulnerability affecting the DatabaseName::read function.
What versions are affected by CVE-2017-9432?
CVE-2017-9432 affects libstaroffice versions prior to 0.0.4.
Who is impacted by CVE-2017-9432?
Users and organizations that utilize vulnerable versions of libstaroffice for document processing are at risk due to CVE-2017-9432.