Skip to content
Fencer Intel
medium 5.5

CVE-2018-1000654 json

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 as…

published 8y ago modified 4mo ago also EUVD-2018-1985

cvss
5.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

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 asn1Paser against the POC due to an issue in _asn1_expand_object_id(p_tree), after a long time, the program will be killed. This attack appears to be exploitable via parsing a crafted file.

Patch / fix

  • libtasn1-6 Debian 14, Debian 13, Debian 12 4.14-2

debian advisories DEBIAN-CVE-2018-1000654

  • libtasn1-6 Ubuntu Pro 16.04 LTS 4.7-3ubuntu0.16.04.3+esm2

ubuntu advisories UBUNTU-CVE-2018-1000654

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libtasn1 SLES 12 SP2-BCL 3.7-13.7.1
  • libtasn1 SLE Module for Desktop Applications 15, SLE Module for Basesystem 15 SP1, SLE Module for Basesystem 15 4.13-4.5.1
  • libtasn1 SLES for SAP 12 SP4, SLES for SAP 12 SP3, SLES 12 SP4 +5 more 4.9-3.10.1

suse advisories SUSE-SU-2022:3797-1SUSE-SU-2019:1372-2SUSE-SU-2019:1379-1SUSE-SU-2019:1372-1

  • libtasn1 openSUSE Tumbleweed 4.17.0-1.2
  • libtasn1 openSUSE Leap 15.1, openSUSE Leap 15.0 4.13-lp151.4.3.1

opensuse advisories openSUSE-SU-2024:11001-1openSUSE-SU-2019:1498-1

  • libtasn1 Alpine 3.24, Alpine 3.23, Alpine 3.22 +14 more 4.14-r0
  • libtasn1 Alpine 3.7 4.12-r4

alpine advisories ALPINE-CVE-2018-1000654

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2018-1000654 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000654 updated cvss 4.0

libtasn1: Infinite loop in _asn1_expand_object_id(ptree) leads to memory exhaustion

  • Red Hat Enterprise Linux 6 libtasn1, libtasn1-tools Red Hat Enterprise Linux 7 libtasn1, libtasn1-tools
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 8 libtasn1, libtasn1-tools, mingw-libtasn1, mingw32-libtasn1, mingw64-libtasn1
    affected: no fix available, no fix planned “Will not fix”
  • Red Hat Satellite 6 libtasn1 Red Hat Virtualization 4 libtasn1
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • gitlab.com https://gitlab.com/gnutls/libtasn1/issues/4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.