Skip to main content
CVE-2024-39249VulnerabilityPublished Updated

CVE-2024-39249: async · n/a

Affects asyncSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
npmasyncpkg:npm/asyncOther threatsAffected
  • <=2.6.4
  • <=3.2.5
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Avoid using vulnerable Async versions (<= 2.6.4 and <= 3.2.5) in production environments, especially where input sources cannot be fully trusted. 2. Monitor official Async library repositories and security advisories for patches or updates addressing this vulnerability and apply them promptly once available. 3. Implement input validation and sanitization to restrict or sanitize inputs reaching the autoinject function to prevent maliciously crafted regex payloads. 4. Employ runtime resource limits such as CPU timeouts or regex execution timeouts to mitigate potential ReDoS impact. 5. Use Web Application Firewalls (WAFs) or Intrusion Prevention Systems (IPS) to detect and block suspicious input patterns targeting regex parsing. 6. Conduct code reviews and security testing focusing on regex usage in your codebase to identify and remediate similar ReDoS risks. 7. Consider isolating or sandboxing components that use vulnerable regexes to limit the blast radius of potential DoS attacks. 8. Maintain comprehensive monitoring and alerting on service performance metrics to detect early signs of DoS conditions.

Description

Async <= 2.6.4 and <= 3.2.5 are vulnerable to ReDoS (Regular Expression Denial of Service) while parsing function in autoinject function. NOTE: this is disputed by the supplier because there is no realistic threat model: regular expressions are not used with untrusted input.

References

Community reviews

Loading reviews…