CVE-2016-4008: The _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…
Noroxi assessment
Priority: Monitor (action score 32/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: 29.4% (FIRST EPSS); higher than 98.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: libtasn1-6 (Debian:12) 4.8-1; libtasn1-3 (Debian:7) 2.13-2+deb7u3; libtasn1-6 (Debian:8) 4.2-3+deb8u2.
Low priority for now. Upgrade to libtasn1-6 (Debian:12) 4.8-1; libtasn1-3 (Debian:7) 2.13-2+deb7u3; libtasn1-6 (Debian:8) 4.2-3+deb8u2 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
The _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, allows remote attackers to cause a denial of service (infinite recursion) via a crafted certificate.
- Published
- May 5, 2016
- Updated
- Jun 16, 2026
- EPSS
- 29.4% · 98th percentile
- CWE
- CWE-399
Report tools
Action score
32
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 9 / 30 · 29.4%
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 |
|---|---|---|
| gnu | libtasn1 | cpe:2.3:a:gnu:libtasn1 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.10
- canonical ubuntu linux16.04
- fedoraproject fedora22
- fedoraproject fedora23
- fedoraproject fedora24
- gnu libtasn1up to 4.7 inclusive
- opensuse opensuse13.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libtasn1-6 | before 4.8-1 | 4.8-1 |
| Debian:7 | libtasn1-3 | before 2.13-2+deb7u3 | 2.13-2+deb7u3 |
| Debian:8 | libtasn1-6 | before 4.2-3+deb8u2 | 4.2-3+deb8u2 |
| openSUSE:Tumbleweed | libtasn1 | before 4.9-1.3 | 4.9-1.3 |
| SUSE:Linux Enterprise Desktop 12 | libtasn1 | before 3.7-11.1 | 3.7-11.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | libtasn1 | before 1.5-1.34.1 | 1.5-1.34.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…37Monitor
- CVE-2018-6003An issue was discovered in the _asn1_decode_simple_ber function in decoding.c in GNU Libtasn1 before 4.13.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2015-3622May 12, 2015 · The _asn1_extract_der_octet function in lib/decoding.c in GNU Libtasn1 before 4.5 allows remote attackers to cause a denial of service…27Monitor
- Later →CVE-2017-10790Jul 1, 2017 · The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input…31Monitor
- Later →CVE-2018-1000654Aug 20, 2018 · GNU Libtasn1-4.13 libtasn1-4.13 version libtasn1-4.13, libtasn1-4.12 contains a DoS, specifically CPU usage will reach 100% when running…23Monitor
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 |
|---|---|---|
| debian:libtasn1-3 | 2.13-2+deb7u3 · Debian:7 | Package registry (OSV) |
| debian:libtasn1-6 | 4.8-1 · Debian:12 | Package registry (OSV) |
| opensuse:libtasn1 | 4.9-1.3 · openSUSE:Tumbleweed | Package registry (OSV) |
| suse:libtasn1 | 1.5-1.34.1 · SUSE:Linux Enterprise Software Development Kit 11 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · 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.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
CVSS:3.0/AV:N/AC:H/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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (12 more)Show less
- git.savannah.gnu.org/gitweb/?p=libtasn1.git%3Ba=commit%3Bh=f435825c0f527a8e52e6ffbc3ad0bc60531d537e
- lists.fedoraproject.org/pipermail/package-announce/2016-April/182299.html
- lists.fedoraproject.org/pipermail/package-announce/2016-April/182907.html
- lists.fedoraproject.org/pipermail/package-announce/2016-April/183221.html
- lists.opensuse.org/opensuse-updates/2016-06/msg00047.html
- lists.opensuse.org/opensuse-updates/2016-06/msg00097.html
- www.debian.org/security/2016/dsa-3568
- www.openwall.com/lists/oss-security/2016/04/11/3
- www.ubuntu.com/usn/USN-2957-1
- www.ubuntu.com/usn/USN-2957-2
- lists.gnu.org/archive/html/help-libtasn1/2016-04/msg00009.html
- security.gentoo.org/glsa/201703-05
Vendor advisories and official records. Exploit/PoC links are deliberately left out.