Skip to main content
CVE-2024-38997VulnerabilityPublished Updated

CVE-2024-38997: ratio-swiper · n/a

Affects ratio-swiperSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% 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:L/I:L/A:N

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
npmadolph_dudu/ratio-swiperpkg:npm/adolph_dudu/ratio-swiperOther threatsAffected
  • =0.0.2
Fixed in–

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

AI-suggested

To mitigate CVE-2024-38997, organizations should first identify if they use the adolph_dudu ratio-swiper library version 0.0.2 in their applications. Immediate steps include: 1) Avoid using or deploying the vulnerable version until a patch is released. 2) Implement strict input validation and sanitization to prevent malicious property injection into objects. 3) Use security-focused JavaScript libraries or frameworks that handle prototype pollution safely. 4) Monitor official sources for patches or updates and apply them promptly once available. 5) Conduct code reviews and static analysis to detect unsafe usage of extendDefaults or similar functions. 6) Employ runtime protections such as Content Security Policy (CSP) to limit the impact of potential code execution. 7) Consider isolating or sandboxing components using this library to reduce blast radius. These targeted actions go beyond generic advice and address the specific nature of prototype pollution vulnerabilities.

Description

adolph_dudu ratio-swiper v0.0.2 was discovered to contain a prototype pollution via the function extendDefaults. This vulnerability allows attackers to execute arbitrary code or cause a Denial of Service (DoS) via injecting arbitrary properties.

References

Community reviews

Loading reviews…