LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10790: The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and cras...

The _asn1_check_identifier function in GNU Libtasn1 through 4.12 causes a NULL pointer dereference and crash when reading crafted input that triggers assignment of a NULL value within an asn1_node structure. It may lead to a remote denial of service attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-10790 is a crash bug in GNU Libtasn1 through 4.12. Crafted input can trigger a NULL pointer dereference while ASN.1 identifiers are checked. The main business risk is service disruption if an exposed application processes attacker-controlled ASN.1 data.

Executive priority

Treat this as a routine but time-bounded infrastructure patching issue. It can cause outages in affected services, but the provided evidence does not support emergency handling for active exploitation or code execution.

Technical view

The issue is in _asn1_check_identifier, where crafted input can cause assignment of a NULL value inside an asn1_node structure and then a crash. The provided sources describe potential remote denial of service, but do not provide CVSS scoring, detailed affected package versions, or exploit telemetry.

Likely exposure

Exposure is most likely on systems running GNU Libtasn1 through 4.12, including distribution packages such as libtasn1-6. Risk depends on whether local or network-facing software accepts untrusted ASN.1 content through this library.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The described impact is denial of service, not code execution. Exploitation requires a path for crafted ASN.1 input to reach vulnerable Libtasn1 parsing logic.

Researcher notes

The bundle identifies the vulnerable function and broad version boundary, but affected product data is incomplete. Distro advisories should be used for exact package status because Linux vendors often backport fixes without changing upstream version numbers.

Mitigation direction

  • Inventory systems and containers containing GNU Libtasn1 or libtasn1-6 packages.
  • Apply vendor security updates from the relevant Linux distribution advisory.
  • Prioritize internet-facing services that parse untrusted ASN.1 data.
  • Check vendor guidance for fixed versions and backported package names.
  • Reduce exposure where untrusted ASN.1 input is unnecessary or externally reachable.

Validation and detection

  • Confirm installed Libtasn1 package versions across hosts, images, and appliances.
  • Map applications that link to or depend on libtasn1 libraries.
  • Review vendor advisories for whether installed packages include the fix.
  • Verify package updates through distribution security metadata, not upstream version strings alone.
  • Monitor service logs for unexplained crashes in ASN.1 parsing paths.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-10790 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.