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

Warn if recovery mode available #509

Open
iandunn opened this issue Feb 1, 2023 · 4 comments
Open

Warn if recovery mode available #509

iandunn opened this issue Feb 1, 2023 · 4 comments

Comments

@iandunn
Copy link
Member

iandunn commented Feb 1, 2023

It's a known issue that attackers can bypass security plugins by triggering recovery mode. Core mitigates that as best it can, but it's still a possibility. There isn't a way for plugins to opt-out (other than completely disabling the fatal error handler), but it may be reasonable to add a warning to Site Health. That could inform users of the risk of leaving it enabled, so they can judge for themselves, and disable it if they want.

@TimothyBJacobs
Copy link
Member

It's not that Core mitigates it. You shouldn't be able engage recovery mode without the user first taking action via an emailed link. If there is a way to bypass that we should fix it in Core.

@iandunn
Copy link
Member Author

iandunn commented Feb 1, 2023

You're right, I didn't say that clearly. What I meant was that, in the context of this plugin, an attacker could bypass 2FA if they have access to a compromised email account. That's not necessarily a problem for a WAF plugin or something, but the whole point of this plugin is to protect against situations where the user's password and/or email account are compromised.

@TimothyBJacobs
Copy link
Member

Gotcha, understood. I think we need to be very careful about the wording. I think a lot of users would take it as a strong recommendation to turn off Recovery Mode, since it's effectively being communicated by Core.

@jeffpaul
Copy link
Member

jeffpaul commented Dec 3, 2024

@iandunn @TimothyBJacobs do you have any input on how this should be phrased and presented within Site Health to make this a bit more actionable for a contributor to come through and help with a PR?

@jeffpaul jeffpaul added this to the Future Release milestone Dec 3, 2024
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

3 participants