LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41737: In Faust 2.23.1, an input file with the lines "// r visualisation tCst" and "//process = +: L: abM-^Q;" and...

In Faust 2.23.1, an input file with the lines "// r visualisation tCst" and "//process = +: L: abM-^Q;" and "process = route(3333333333333333333,2,1,2,3,1) : *;" leads to stack consumption.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-41737 is a denial-of-service issue in Faust 2.23.1. A specially crafted Faust input can consume stack resources and make the process unavailable. The public record does not identify broader affected products, a fixed version, or active exploitation.

Executive priority

Treat as a targeted availability risk for environments that expose Faust processing to untrusted input. Prioritize quickly if Faust is internet-facing or part of customer-submitted content workflows; otherwise handle through normal dependency remediation.

Technical view

The CVE describes stack consumption in Faust 2.23.1 triggered by malformed input processed by Faust. It is classified as CWE-674 and scored CVSS 7.5 for availability impact only. The source bundle lists no CPEs and no explicit remediation version.

Likely exposure

Exposure is most likely where Faust 2.23.1 processes untrusted or user-supplied Faust source, including build systems, web services, teaching platforms, or automation pipelines. Systems using Faust only with trusted local files have lower practical exposure.

Exploitation context

The bundle marks this CVE as not in KEV and provides no cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated availability impact, but exploit maturity and real-world targeting are not established by the supplied sources.

Researcher notes

Evidence is limited. The CVE record names Faust 2.23.1 and stack consumption, but affected CPEs, fixed version, and exploit status are not provided. Use the GitHub issue and referenced repository tree as primary leads for root-cause and patch validation.

Mitigation direction

  • Inventory Faust usage and confirm whether version 2.23.1 is present.
  • Check Faust project guidance for fixed releases or recommended commits.
  • Avoid processing untrusted Faust input until remediation is confirmed.
  • Run Faust processing in isolated, resource-limited environments.
  • Monitor the referenced GitHub issue for maintainer guidance.

Validation and detection

  • Identify services, CI jobs, or tools that invoke Faust.
  • Confirm whether any workflow accepts external Faust source files.
  • Verify installed Faust versions against the affected 2.23.1 record.
  • Review monitoring for crashes or stack exhaustion in Faust processes.
  • Track remediation status against official Faust references.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-674: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41737 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-41737Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-674 · source CWE mapping

Uncontrolled Recursion

Uncontrolled Recursion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.