lib0 `readUint8Array` performs an unbounded read past the end of the decoder’s view, disclosing adjacent process memory
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
Description
A missing bounds check in the binary decoder in lib0, versions 0.2.1-0.2.117 and earlier and 1.0.0-rc.32 and earlier, lets any unauthenticated remote peer read adjacent process memory and receive it back. readUint8Array never compares the wire-supplied length against the decoder's own view, so one over-long length prefix returns whatever the host process allocated next: other tenants' document content, personal data, and live bearer session tokens**, recovered in full and at will. An attacker who can supply bytes to a lib0 decoder which means any peer that can open a socket, including before authentication reads adjacent process memory and, where the consumer echoes, stores or re-serves the decoded value, receives it back. This is patched in version 0.2.118 and 1.0.0-rc.33.
Text from CVE List
Affected versions 2
- lib0affected: <= 0.2.1-0.2.117CVE List
- lib0affected: <= 1.0.0-rc.32CVE List