libdwarf_project is a technology vendor producing software and infrastructure products. As a software provider, libdwarf_project's broad product portfolio across multiple domains—including operating systems, cloud infrastructure, enterprise applications, databases, networking, and security tools—creates a large attack surface. Additionally, long support cycles, widespread deployment, and continuous feature development contribute to the accumulation of discovered vulnerabilities over time. Major vendors typically report higher CVE counts not necessarily due to inferior security, but because of greater exposure to security research, responsible disclosure practices, and the sheer complexity of maintaining multiple product lines and legacy systems. Regular security assessments and patching of libdwarf_project's products are critical for organizations running their software in production environments.
SecUtils has indexed 45 known vulnerabilities from libdwarf_project. This includes 6 critical-severity issues and 14 high-severity issues that represent significant risk. These vulnerabilities affect 3 distinct products across libdwarf_project's portfolio, demonstrating the breadth of the vendor's product ecosystem and the importance of comprehensive patch management strategies. Disclosure dates span from 2016 through 2024, reflecting sustained security scrutiny over multiple years. Organizations deploying libdwarf_project products should maintain active vulnerability monitoring, prioritize critical patches, and implement compensating controls where patches cannot be applied immediately.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2016-2091 | 2016-02-08 | 2025-04-12 | 3.3 | 4.3 | Likely |
| CVE-2016-9480 | 2016-11-29 | 2025-04-12 | 9.1 | 6.4 | Likely |
| CVE-2016-7410 | 2017-01-23 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2016-2050 | 2017-01-31 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2015-8750 | 2017-02-13 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-8679 | 2017-02-15 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-8680 | 2017-02-15 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-8681 | 2017-02-15 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2016-5028 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5029 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5030 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5031 | 2017-02-17 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2016-5032 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5033 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5034 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5035 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5036 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5037 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-5038 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5039 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5040 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5042 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5043 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5044 | 2017-02-17 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-7510 | 2017-02-17 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2016-7511 | 2017-02-17 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2016-5027 | 2017-02-24 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2016-9558 | 2017-02-28 | 2025-04-20 | 9.8 | 7.5 | Likely |
| CVE-2016-9275 | 2017-03-23 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-9276 | 2017-03-23 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2016-5041 | 2017-04-10 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-9052 | 2017-05-18 | 2025-04-20 | 9.8 | 7.5 | Likely |
| CVE-2017-9053 | 2017-05-18 | 2025-04-20 | 9.1 | 6.4 | Likely |
| CVE-2017-9054 | 2017-05-18 | 2025-04-20 | 9.8 | 7.5 | Likely |
| CVE-2017-9055 | 2017-05-18 | 2025-04-20 | 9.8 | 7.5 | Likely |
| CVE-2015-8538 | 2017-06-07 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-9998 | 2017-06-28 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2014-9482 | 2018-01-16 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-14249 | 2019-07-24 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2022-32200 | 2022-06-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2022-34299 | 2022-06-23 | 2024-11-21 | 8.1 | 5.8 | Likely |
| CVE-2022-39170 | 2022-09-02 | 2024-11-21 | 8.8 | - | - |
| CVE-2020-27545 | 2023-04-16 | 2025-02-06 | 6.5 | - | - |
| CVE-2020-28163 | 2023-04-16 | 2025-02-06 | 6.5 | - | - |
| CVE-2024-2002 | 2024-03-18 | 2025-04-09 | 7.5 | - | - |
SecUtils aggregates National Vulnerability Database (NVD) and MITRE records for libdwarf_project by normalizing vendor identifiers across diverse data sources, mapping vendor names to their associated product lines, and collecting all known vulnerabilities under a unified vendor context. For every CVE associated with libdwarf_project's products, we extract and structure Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) categories, CVSS severity metrics, and reference links to enable rapid vulnerability identification and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and vendor vulnerability tracking.