REDHAT-BUG-1385689: Medium severity libdwarf libdwarf vulnerability

Published Oct 17, 2016

Updated

An out of bounds heap read vulnerability was found in dwarfgetsizeofval triggered by invoking dwarfdump command on crafted file.

Upstream patches:

https://sourceforge.net/p/libdwarf/code/ci/2d14a7792889e33bc542c28d0f3792964c46214f/#diff-13 https://sourceforge.net/p/libdwarf/code/ci/efe48cad0693d6994d9a7b561e1c3833b073a624/#diff-2

CVE assignment:

http://seclists.org/oss-sec/2016/q4/144

Affected Software

1 affected component

libdwarf libdwarf

Event History

Oct 17, 2016

Data Sourced

via Red Hat·01:55 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What must an attacker provide to trigger this issue?

The attacker must cause dwarfdump to process a crafted file. The vulnerable code path is _dwarf_get_size_of_val, where the crafted input can trigger an out-of-bounds heap read.

Which systems are realistically exposed?

Systems are exposed where dwarfdump is used to inspect files supplied by an untrusted source. The provided information does not establish that merely having libdwarf installed, without invoking dwarfdump on a crafted file, triggers the issue.

What can be done if patching is not immediately possible?

Avoid running dwarfdump on untrusted or externally supplied files until the upstream fixes are applied. Restrict access to workflows that automatically invoke dwarfdump on attacker-controlled input.

REDHAT-BUG-1385689: Medium severity libdwarf libdwarf vulnerability

Affected Software

Event History

Frequently Asked Questions

What must an attacker provide to trigger this issue?

Which systems are realistically exposed?

What can be done if patching is not immediately possible?

Company

Resources

Contact

Frequently Asked Questions

What must an attacker provide to trigger this issue?

Which systems are realistically exposed?

What can be done if patching is not immediately possible?