Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
jimstir opened this issue Jun 13, 2024 · 0 comments

Comments

@jimstir
Copy link
Collaborator

jimstir commented Jun 13, 2024

Reference Issue: vacp2p/rfc#449
Author: staheri14

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant