-
Notifications
You must be signed in to change notification settings - Fork 335
Add security response about wire.com DoS and HTML injection #3050
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,21 @@ | ||
| # 2023-01-04 - Outage of wire.com caused by a DoS attack | ||
|
|
||
| Last updated: 2023-01-19 | ||
|
|
||
| ## What happened? | ||
| On Tuesday, 2023-01-04, the Wire website wire.com was affected by an outage caused by a Denial-of-Service attack. This outage only concerns the wire.com website and none of the services provided by Wire. | ||
|
|
||
| ## What was the impact identified? | ||
| Several outages of short periods (7min, 2min, 3min, 4min) have been identified beginning from UTC 05:13. | ||
|
|
||
| ## Are Wire installations affected? | ||
| Wire/wire-server was not affected by the wire.com website outage. | ||
|
|
||
| ## Timeline | ||
|
|
||
| *2023-01-04 05:13*: The website monitor triggered an alert on a server issue.\ | ||
| *2023-01-04 05:16*: The responsible team of the service provider responded and saw an outage for periods of 7 minutes beginning from UTC 05:13, 2 minutes (UTC 05:29), 3 minutes (UTC 05:36) and 4 minutes (UTC 05:43).\ | ||
| *2023-01-04/11:34*: Wire was informed about an attempted DoS attack on wire.com by the service provider which manually blocked the IP address in the process.\ | ||
| *2023-01-04 09:15*: Wire started an internal investigation to check whether other systems have been affected, which was not the case.\ | ||
| *2023-01-04 14:30*: Wire contacted the service provider for more details on the incident as well as the corresponding log files.\ | ||
| *2023-01-18 09:53*: Wire received the incident report from the service provider.\ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| # 2023-01-19 - Security Advisory: HTML Injection in wire.com | ||
|
|
||
| Last updated: 2023-01-31 | ||
|
|
||
| ## Introduction | ||
| On the 16st January, 2023, we were informed about a possible vulnerability in our website wire.com. A get-parameter on the page https://wire.com/en/pricing/ was vulnerable to HTML injection. As the website wire.com is not directly maintained by Wire, the service provider was directly informed about the disclosed issue. The patch that fixed that vulnerability was rolled out on the 18th of January. | ||
|
|
||
| ## Impact | ||
| An adversary would have been able to inject arbitrary HTML code through the parameter and send that link to someone else which would show them e.g., a defaced website or potentially inject JavaScript. | ||
|
|
||
| ## Are Wire installations affected? | ||
| Wire/wire-server is not affected by this vulnerability as our website wire.com is completely separated from the Wire backend. | ||
|
|
||
| ## Are Wire clients affected? | ||
| Wire clients are not affected by this vulnerability. | ||
|
|
||
| ## Credits | ||
| We thank [Umar Ahmed](http://linkedin.com/in/theumar9) for reporting this vulnerability. | ||
|
sanojwr marked this conversation as resolved.
Outdated
|
||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.