Skip to main content
No exploitation reportedFix available

CVE-2018-1000654

No exploitation reported by the sources we read.

  • Published2018-08-20

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2018-08-2019:31CVE publishedNVD

Versions per branch

NVD
Gnu libtasn1
BranchAffectedFixed in
4.12= 4.12no fix published
4.13= 4.13no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • libtasn1SUSE:Linux Enterprise Software Development Kit 12 SP4all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Software Development Kit 12 SP3all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Server for SAP Applications 12 SP4all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Server for SAP Applications 12 SP3all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Server 12 SP4all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Server 12 SP3all versions · fixed in 4.9-3.10.1
  • libtasn1SUSE:Linux Enterprise Server 12 SP2-BCLall versions · fixed in 3.7-13.7.1
  • libtasn1SUSE:Linux Enterprise Module for Desktop Applications 15all versions · fixed in 4.13-4.5.1

33 more package ranges on OSV.dev

Vendor advisories

  • CVE-2018-1000654 Red Hat Product Security18 known affected

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

    libtasn1 as a component of Red Hat Enterprise Linux 6 · libtasn1-devel as a component of Red Hat Enterprise Linux 6 · libtasn1-tools as a component of Red Hat Enterprise Linux 6 · +15 more

Full record on NVD

Fix

  1. No fix available, says the vendor Red Hat Product Security CVE-2018-1000654 · 3 productsFix deferred
  2. No fix planned, says the vendor Red Hat Product Security CVE-2018-1000654 · 15 productsWill not fix

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Published
2018-08-20
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-g69v-w5wh-rhwv

Frequently asked questions

What is CVE-2018-1000654?

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.

Is CVE-2018-1000654 actively exploited?

Active exploitation of CVE-2018-1000654 has not been confirmed. Its EPSS score was 2.0% on 2026-11-09, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2018-1000654?

CVE-2018-1000654 has a CVSS v3 base score of 5.5 (MEDIUM severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H.

Running libtasn1? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record