Skip to main content
CVE-2024-29433VulnerabilityPublished Updated

CVE-2024-29433: alldata · n/a

Affects alldataSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Apr 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
npmalldatapkg:npm/alldataOther threatsAffected
  • =0.4.6
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. Immediately identify and inventory all systems running Alldata v0.4.6 with FASTJSON components. 2. Apply any available vendor patches or updates as soon as they are released. 3. If patches are unavailable, implement strict input validation and sanitization to reject untrusted or malformed serialized data. 4. Employ network segmentation and firewall rules to restrict access to vulnerable services only to trusted internal networks. 5. Monitor network traffic and logs for unusual deserialization attempts or command execution patterns. 6. Use application-layer firewalls or runtime application self-protection (RASP) tools to detect and block exploitation attempts. 7. Consider disabling or replacing FASTJSON with safer serialization libraries if feasible. 8. Conduct regular security assessments and penetration testing focusing on deserialization vulnerabilities. 9. Educate development and operations teams about secure deserialization practices to prevent similar issues in the future.

Description

A deserialization vulnerability in the FASTJSON component of Alldata v0.4.6 allows attackers to execute arbitrary commands via supplying crafted data.

References

Community reviews

Loading reviews…