In elfutils 0.175, there is a buffer over-read in the ebl_object_note function in eblobjnote.c in libebl.
Noroxi assessment
Priority: Monitor (action score 22/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: 1.5% (FIRST EPSS); higher than 73.8% of all records.
- Someone with local access to the system 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: elfutils (Alpine:v3.12) 0.176-r0; elfutils (Debian:12) 0.176-1; elfutils (openSUSE:Tumbleweed) 0.185-3.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to elfutils (Alpine:v3.12) 0.176-r0; elfutils (Debian:12) 0.176-1; elfutils (openSUSE:Tumbleweed) 0.185-3.1 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
In elfutils 0.175, there is a buffer over-read in the ebl_object_note function in eblobjnote.c in libebl. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted elf file, as demonstrated by eu-readelf.
- Published
- Jan 28, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.5% · 74th percentile
- CWE
- CWE-125
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
|---|---|---|
| elfutils project | elfutils | cpe:2.3:a:elfutils_project:elfutils |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- elfutils project elfutils0.175
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.12 | elfutils | before 0.176-r0 | 0.176-r0 |
| Debian:12 | elfutils | before 0.176-1 | 0.176-1 |
| openSUSE:Tumbleweed | elfutils | before 0.185-3.1 | 0.185-3.1 |
| Red Hat:enterprise_linux:8::baseos | elfutils | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-debuginfo | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-debugsource | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-default-yama-scope | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-devel | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-libelf | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-libelf-debuginfo | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-libelf-devel | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-libs | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::baseos | elfutils-libs-debuginfo | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::crb | elfutils-devel-static | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| Red Hat:enterprise_linux:8::crb | elfutils-libelf-devel-static | before 0:0.176-5.el8 | 0:0.176-5.el8 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | dwarves | before 1.22-150300.7.3.1 | 1.22-150300.7.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | dwarves | before 1.22-150300.7.3.1 | 1.22-150300.7.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | elfutils | before 0.177-150300.11.3.1 | 0.177-150300.11.3.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | elfutils | before 0.177-150300.11.3.1 | 0.177-150300.11.3.1 |
Same product
elfutils project: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-16402libelf/elf_end.c in elfutils 0.173 allows remote attackers to cause a denial of service (double free and application crash) or possibly have40Plan
- CVE-2018-8769elfutils 0.170 has a buffer over-read in the ebl_dynamic_tag_name function of libebl/ebldynamictagname.c because SYMTAB_SHNDX is unsupported31Monitor
- CVE-2014-0172Integer overflow in the check_section function in dwarf_begin_elf.c in the libdw library, as used in elfutils 0.153 and possibly through 0.128Monitor
- CVE-2019-7149A heap-based buffer over-read was discovered in the function read_srclines in dwarf_getsrclines.c in libdw in elfutils 0.175.27Monitor
- CVE-2018-18520An Invalid Memory Address Dereference exists in the function elf_end in libelf in elfutils through v0.174.27Monitor
- CVE-2014-9447Directory traversal vulnerability in the read_long_names function in libelf/elf_begin.c in elfutils 0.152 and 0.161 allows remote attackers 27Monitor
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 |
|---|---|---|
| alpine:elfutils | 0.176-r0 · Alpine:v3.12 | Package registry (OSV) |
| debian:elfutils | 0.176-1 · Debian:12 | Package registry (OSV) |
| opensuse:dwarves | 1.22-150300.7.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:elfutils | 0.177-150300.11.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| red hat:elfutils | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-debuginfo | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-debugsource | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-default-yama-scope | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-devel | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-devel-static | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:elfutils-libelf | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-libelf-debuginfo | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-libelf-devel | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-libelf-devel-static | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::crb | Package registry (OSV) |
| red hat:elfutils-libs | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:elfutils-libs-debuginfo | 0:0.176-5.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| suse:dwarves | 1.22-150300.7.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
| suse:elfutils | 0.177-150300.11.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-905 · Oct 30, 2020(OpenShift Güvenlik Güncellemesi)
Technical details
Attack conditions
- Someone with local access to the system 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
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:L/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.