CVE-2024-21522: All versions of the package audify are vulnerable to Improper Validation of Array Index when frameSize is p...
All versions of the package audify are vulnerable to Improper Validation of Array Index when frameSize is provided to the new OpusDecoder().decode or new OpusDecoder().decodeFloat functions it is not checked for negative values. This can lead to a process crash.
Security readout for executives and security teams
Plain-English summary
CVE-2024-21522 affects the npm package audify. A negative frameSize value passed into OpusDecoder decode functions can crash the process. The impact described is availability loss, not data theft or code execution. Risk is highest where audify handles untrusted or remotely influenced audio-processing inputs.
Executive priority
Prioritize remediation for externally reachable services or products that process user-supplied audio using audify. The business risk is service disruption, not confirmed data compromise. If audify is only used in internal trusted workflows, handle through normal vulnerability management unless reliability requirements are strict.
Technical view
The issue is CWE-129, improper validation of an array index. The source bundle states new OpusDecoder().decode and decodeFloat do not check frameSize for negative values, causing a process crash. CVSS 3.1 is 7.5 with network attack vector, no privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is limited to applications that include audify and use its OpusDecoder decode or decodeFloat paths. Internet-facing or multi-tenant services are more exposed if remote users can influence audio data or frameSize. Systems without audify, or with tightly validated internal inputs, are less likely exposed.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. It does include proof-oriented signals, including CVSS exploit maturity marked P and a public gist reference. Treat this as plausible denial-of-service risk, but do not assume real-world exploitation without additional evidence.
Researcher notes
The source evidence names audify, all versions, and OpusDecoder decode/decodeFloat frameSize validation. It does not provide a vendor patch in the bundle. Research should focus on dependency reachability, input control, crash reproducibility in a safe test environment, and whether upstream has released corrected validation.
Mitigation direction
Inventory applications for the audify package and affected OpusDecoder usage.
Check Snyk and upstream audify guidance for fixed versions or maintainer recommendations.
Validate and reject negative frameSize values before calling decode or decodeFloat.
Reduce exposure of audio-processing endpoints that accept untrusted input.
Use process supervision and rate controls to limit crash impact.
Validation and detection
Search dependency manifests and lockfiles for audify.
Review code paths calling new OpusDecoder().decode or decodeFloat.
Confirm whether frameSize can be influenced by users or network input.
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-129: 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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-129 · source CWE mapping
Improper Validation of Array Index
Improper Validation of Array Index represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.