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

Simple registration and client aliveness #234

Closed
chrysn opened this issue Apr 15, 2020 · 0 comments
Closed

Simple registration and client aliveness #234

chrysn opened this issue Apr 15, 2020 · 0 comments

Comments

@chrysn
Copy link
Member

@chrysn chrysn commented Apr 15, 2020

Entering #233 led to a curious thought:

What if I have a firewalled environment (yeah ok I don't believe in them, but some do), a rather open RD inside accessible from outside, and someone wants to probe a local device.

The attacker can simply[1] send a POST /.well-known/core to the RD with a fake source address, let the RD query the victim's .well-known/core and then read it via the RD.

Possible mitigation: ensure client aliveness. The Echo option provides that and is still easier to implement than POST when .well-known/core needs fragmentation. Would that still be simple enough?

[1]: I suppose well-behaved firewalls do source filtering, but what do I know of them

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