The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input that
The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input that triggers assignment of a NULL value within an asn1_node structure. It may lead to a remote denial of service attack.
- Published
- Jul 1, 2017
- Updated
- Jun 16, 2026
- EPSS
- 5.0% · 92th percentile
- CWE
- CWE-476
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 5.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| gnu | libtasn1 | cpe:2.3:a:gnu:libtasn1 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- gnu libtasn1up to 4.12 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libtasn1 | before 4.12-r1 | 4.12-r1 |
| Alpine:v3.3 | libtasn1 | before 4.7-r3 | 4.7-r3 |
| Alpine:v3.4 | libtasn1 | before 4.8-r2 | 4.8-r2 |
| Alpine:v3.5 | libtasn1 | before 4.9-r2 | 4.9-r2 |
| Alpine:v3.6 | libtasn1 | before 4.10-r2 | 4.10-r2 |
| Debian:12 | libtasn1-6 | before 4.12-2.1 | 4.12-2.1 |
| Debian:7 | libtasn1-3 | before 2.13-2+deb7u5 | 2.13-2+deb7u5 |
| Debian:8 | libtasn1-6 | before 4.2-3+deb8u4 | 4.2-3+deb8u4 |
| Debian:9 | libtasn1-6 | before 4.10-1.1+deb9u1 | 4.10-1.1+deb9u1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | gnutls | before 3.3.27-3.3.1 | 3.3.27-3.3.1 |
| SUSE:Linux Enterprise High Availability Extension 11 SP4 | gnutls | before 2.4.1-24.39.76.1 | 2.4.1-24.39.76.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | gnutls | before 3.6.2-6.3.1 | 3.6.2-6.3.1 |
| SUSE:OpenStack Cloud 7 | gnutls | before 3.2.15-18.6.1 | 3.2.15-18.6.1 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-46848GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.37Monitor
- CVE-2017-6891Two errors in the "asn1_find_node()" function (lib/parser_aux.c) within GnuTLS libtasn1 version 4.10 can be exploited to cause a stacked-bas37Monitor
- CVE-2018-6003An issue was discovered in the _asn1_decode_simple_ber function in decoding.c in GNU Libtasn1 before 4.13.31Monitor
- CVE-2016-4008The _asn1_extract_der_octet function in lib/decoding.c in GNU Libtasn1 before 4.8, when used without the ASN1_DECODE_FLAG_STRICT_DER flag, a31Monitor
- CVE-2025-13151Stack-based buffer overflow in libtasn1 version: v4.20.0.30Monitor
- CVE-2015-3622The _asn1_extract_der_octet function in lib/decoding.c in GNU Libtasn1 before 4.5 allows remote attackers to cause a denial of service (out-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:libtasn1 | 4.12-r1 · Alpine:v3.10 | Package registry (OSV) |
| debian:libtasn1-3 | 2.13-2+deb7u5 · Debian:7 | Package registry (OSV) |
| debian:libtasn1-6 | 4.12-2.1 · Debian:12 | Package registry (OSV) |
| suse:gnutls | 3.2.15-18.6.1 · SUSE:OpenStack Cloud 7 | 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).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- 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
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
- lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- lists.debian.org/debian-lts-announce/2020/06/msg00026.html
- security.gentoo.org/glsa/201710-11
- usn.ubuntu.com/3547-1/
- www.debian.org/security/2018/dsa-4106
Vendor advisories and official records. Exploit/PoC links are deliberately left out.