When was CVE-2018-6003 disclosed?

CVE-2018-6003 was first published in the National Vulnerability Database on January 22, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-6003 actively exploited?

CVE-2018-6003 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-6003?

CVE-2018-6003 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2018-6003?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-6003, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

CVE-2018-6003

HIGHNVD 7.5

7.5

An issue was discovered in the _asn1_decode_simple_ber function in decoding.c in GNU Libtasn1 before 4.13. Unlimited recursion in the BER decoder leads to stack exhaustion and DoS.

CVSS v3: 7.5
EG Score: —
EPSS: 85.7%
KEV: Not listed

References (14)

cve@mitrehttp://git.savannah.nongnu.org/cgit/libtasn1.git/commit/?id=c593ae84cfcde8fea45787e53950e0ac71e9ca97
cve@mitrehttps://bugzilla.redhat.com/show_bug.cgi?id=1535926
cve@mitrehttps://bugzilla.suse.com/show_bug.cgi?id=1076832
cve@mitrehttps://gitlab.com/gnutls/libtasn1/commit/946565d8eb05fbf7970ea366e817581bb5a90910
cve@mitrehttps://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
cve@mitrehttps://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
cve@mitrehttps://www.debian.org/security/2018/dsa-4106
af854a3a-2127-422b-91ae-364da2661108http://git.savannah.nongnu.org/cgit/libtasn1.git/commit/?id=c593ae84cfcde8fea45787e53950e0ac71e9ca97
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.redhat.com/show_bug.cgi?id=1535926
af854a3a-2127-422b-91ae-364da2661108https://bugzilla.suse.com/show_bug.cgi?id=1076832
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gnutls/libtasn1/commit/946565d8eb05fbf7970ea366e817581bb5a90910
af854a3a-2127-422b-91ae-364da2661108https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E
af854a3a-2127-422b-91ae-364da2661108https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
af854a3a-2127-422b-91ae-364da2661108https://www.debian.org/security/2018/dsa-4106

Is Your Infrastructure Affected by CVE-2018-6003?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2018-6003

Published

Last Modified

References (14)

Weakness Classification(1)

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-6003?

CVE-2018-6003

📅 Published

🔄 Last Modified

🔗 References (14)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-6003?

Published

Last Modified

References (14)

Frequently asked(5)