LiveActive security incident?Get immediate response
CVE Record

CVE-2022-22901: There is an Assertion in 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed at parser_p...

There is an Assertion in 'context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION' failed at parser_parse_function_arguments in /js/js-parser.c of JerryScript commit a6ab5e9.

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

Security readout for executives and security teams

Plain-English summary

CVE-2022-22901 describes a JerryScript parser assertion failure in a specific commit. The public bundle does not show a CVSS score, affected release list, CWE, patch, or real-world impact. Treat it as a potential crash or stability issue until vendor evidence clarifies security impact.

Executive priority

Do not treat this as an emergency based on current evidence. Assign vulnerability management follow-up for embedded JerryScript inventory and vendor-status tracking, especially in products processing untrusted scripts.

Technical view

The report names an assertion failure in parser_parse_function_arguments in /js/js-parser.c: context_p->next_scanner_info_p->type == SCANNER_TYPE_FUNCTION. It is tied to JerryScript commit a6ab5e9. The bundle does not establish affected versions, exploitability, or whether this reaches production builds.

Likely exposure

Exposure is most plausible where JerryScript at or near commit a6ab5e9 is embedded and parses untrusted JavaScript. The sources do not identify affected products, packaged releases, CPEs, or downstream vendors.

Exploitation context

No source in the bundle reports active exploitation, and the CVE is not listed as KEV. The available description only supports an assertion failure report, not weaponized exploitation or confirmed security impact.

Researcher notes

The public metadata is sparse: no CVSS, CWE, affected release, CPE, patch, or exploit evidence is provided. The GitHub issue is the key technical reference. Any impact assessment should distinguish assertion/crash behavior from confirmed security exploitability.

Mitigation direction

  • Check JerryScript project and issue 4916 for vendor guidance or fixed commits.
  • Inventory products and firmware that embed JerryScript.
  • Prioritize systems that parse untrusted or attacker-supplied JavaScript.
  • Avoid assuming all JerryScript releases are affected without vendor confirmation.
  • Track CVE updates for CVSS, CWE, affected versions, and remediation details.

Validation and detection

  • Review SBOMs and source dependencies for JerryScript usage.
  • Identify whether builds include commit a6ab5e9 or nearby vulnerable code.
  • Confirm whether JavaScript input is accepted from untrusted users or networks.
  • Review vendor issue 4916 for resolution status before closing exposure.
  • Document uncertainty where product versions cannot be mapped to the commit.
Prepared
Confidence
medium
Sources
4

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-2022-22901 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

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.