CVE-2017-9054: Critical severity Libdwarf Project Libdwarf vulnerability

Published May 18, 2017
·
Updated

An issue, also known as DW201703-002, was discovered in libdwarf 2017-03-21. In dwarfdecodesleb128chk() a byte pointer was dereferenced just before it was checked for being in bounds, leading to a heap-based buffer over-read.

Affected Software

1 affected component
Libdwarf Project Libdwarf=2017-03-21

Event History

May 18, 2017
CVE Published
via MITRE·06:13 AM
Data Sourced
via MITRE·06:13 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2017-9054?

CVE-2017-9054 has a critical severity score of 9.8 based on the CVSS 3.1 metrics.

2

How do I fix CVE-2017-9054?

To mitigate CVE-2017-9054, you should update to the latest version of the Libdwarf software where the vulnerability has been addressed.

3

What kind of vulnerability is CVE-2017-9054?

CVE-2017-9054 is a heap-based buffer over-read vulnerability that occurs due to improper boundary checks.

4

Who is affected by CVE-2017-9054?

Any software that relies on the affected versions of libdwarf is potentially vulnerable to CVE-2017-9054.

5

What are the potential impacts of CVE-2017-9054?

CVE-2017-9054 can lead to information disclosure or potentially arbitrary code execution due to memory corruption.

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