Baileys has message upsert / hist sync spoofing and app state corruption when using maliciously crafted protocolMessage payload
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.7.22, 7.0.0-rc12
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Baileys is a cocket-based TS/JavaScript API for WhatsApp Web. In versions prior to both 6.7.22 and 7.0.0-rc12, any Baileys session can be sent a malicious payload via the placeholderResendMessage and trigger a fake messages.upsert event with a fake message key and payload. This allows anyone to spoof messages. The same exploit also allows an attacker to corrupt the app state sync system by sending fake key shares, and also allows for history sync spoofing which also serves the same problem, injecting fake previous context or "on-demand" sync. This issue has been fixed in versions 6.7.22 and 7.0.0-rc12.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- WhiskeySockets Baileys
fixed in 6.7.22; From 7.0.0-rc.1 · fixed in 7.0.0-rc12
- WhiskeySockets @whiskeysockets/baileys
fixed in 6.7.22; From 7.0.0-rc.1 · fixed in 7.0.0-rc12
- baileysnpm
fixed in 6.7.22
- @whiskeysockets/baileysnpm
fixed in 6.7.22
- baileysnpm
From 7.0.0-rc.1 · fixed in 7.0.0-rc12
- @whiskeysockets/baileysnpm
From 7.0.0-rc.1 · fixed in 7.0.0-rc12