CVE-2020-27545: libdwarf before 20201017 has a one-byte out-of-bounds read because of an invalid pointer dereference via an invalid line table in a crafted…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.82% (FIRST EPSS); higher than 57.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: azl3 libdwarf 0.9.0-1 on Azure Linux 3.0 0.9.0-1; cbl2 libdwarf 0.9.0 on CBL Mariner 2.0 0.9.0.
Low priority for now. Upgrade to azl3 libdwarf 0.9.0-1 on Azure Linux 3.0 0.9.0-1; cbl2 libdwarf 0.9.0 on CBL Mariner 2.0 0.9.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
libdwarf before 20201017 has a one-byte out-of-bounds read because of an invalid pointer dereference via an invalid line table in a crafted object.
- Published
- Apr 15, 2023
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-763
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libdwarf project | libdwarf | cpe:2.3:a:libdwarf_project:libdwarf |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- libdwarf project libdwarfbefore 2020-10-17
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | dwarfutils | before 20201201-1 | 20201201-1 |
| openSUSE:Leap 15.4 | libdwarf | before 20161124-150000.3.6.1 | 20161124-150000.3.6.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP4 | libdwarf | before 20161124-150000.3.6.1 | 20161124-150000.3.6.1 |
Same product
libdwarf project: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-9055An issue, also known as DW201703-001, was discovered in libdwarf 2017-03-21.40Plan
- CVE-2017-9054An issue, also known as DW201703-002, was discovered in libdwarf 2017-03-21.40Plan
- CVE-2017-9052An issue, also known as DW201703-006, was discovered in libdwarf 2017-03-21.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-34299Jun 23, 2022 · There is a heap-based buffer over-read in libdwarf 0.4.0.32Monitor
- ← EarlierCVE-2022-39170Sep 1, 2022 · libdwarf 0.4.1 has a double free in _dwarf_exec_frame_instr in dwarf_frame.c.35Monitor
- Later →CVE-2020-28163Apr 15, 2023 · libdwarf before 20201201 allows a dwarf_print_lines.c NULL pointer dereference and application crash via a DWARF5 line-table header that…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 libdwarf 0.9.0-1 on Azure Linux 3.0 | 0.9.0-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 libdwarf 0.9.0 on CBL Mariner 2.0 | 0.9.0 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:dwarfutils | 20201201-1 · Debian:12 | Package registry (OSV) |
| opensuse:libdwarf | 20161124-150000.3.6.1 · openSUSE:Leap 15.4 | Package registry (OSV) |
| suse:libdwarf | 20161124-150000.3.6.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-763 · Release of Invalid Pointer or ReferenceCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.