Vulnerability in GNU Libtasn1-4.13 libtasn1-4.13 (CVE-2018-1000654)

Summary

Vulnerability in GNU Libtasn1-4.13 libtasn1-4.13 (CVE-2018-1000654). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) NVD OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2018-1000654 has been found in GNU Libtasn1-4.13 libtasn1-4.13.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "GNU Libtasn1-4.13 libtasn1-4.13 CVE-2018-1000654" on the vendor's site.

CVE-2018-1000654 (GNU Libtasn1-4.13 libtasn1-4.13)
Attack vector: local / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in GNU Libtasn1-4.13 libtasn1-4.13.

📍 Affected scope

Check the vendor advisory for the affected versions of GNU Libtasn1-4.13 libtasn1-4.13.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで GNU Libtasn1-4.13 libtasn1-4.13 を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Fix status by distribution

Fixed packages published by each distribution for this CVE

Alpine Linux ALPINE-CVE-2018-1000654 libtasn1 Fixed in: 4.14-r0
Debian DEBIAN-CVE-2018-1000654 libtasn1-6 Fixed in: 4.14-2