Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

14/WAKU2-MESSAGE: Lack of integrity for contentTopic and timestamp in waku messages #449

Closed
staheri14 opened this issue Aug 6, 2021 · 2 comments

Comments

@staheri14
Copy link
Contributor

staheri14 commented Aug 6, 2021

Problem

The problem is that currently there is no method to ensure the integrity of the contentTopic and timestamp fields of waku messages. As such, an adversarial node can tamper with these fields without being caught. This can be exploited for censorship, e.g., the attacker can make the message unavailable by changing its timestamp to a time in the past. Similarly, the adversary may amend the contentTopic and make it unreachable to the intended peers. The adversarial peer can be a relay node or a store node.

Acceptance Criteria

  • Investigate the potential attacks related to this issue
  • To sketch out potential solutions
@staheri14 staheri14 changed the title 14/WAKU2-MESSAGE: Lack of integrity for contentTopic and `timestamp in waku messages 14/WAKU2-MESSAGE: Lack of integrity for contentTopic and timestamp in waku messages Aug 6, 2021
@staheri14
Copy link
Contributor Author

staheri14 commented Aug 6, 2021

FYI: @oskarth, @jm-clius

@jimstir
Copy link
Contributor

jimstir commented Jun 13, 2024

Issue moved here

@jimstir jimstir closed this as completed Jun 13, 2024
@jimstir jimstir closed this as not planned Won't fix, can't repro, duplicate, stale Jun 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants