Microsoft Security Advisory CVE-2024-26190 : Microsoft QUIC Denial of Service Vulnerability
まだ誰も着手していません。
評価
- 難易度
- 1/5
- 見積もり時間
- 1時間未満
- 初心者へのやさしさ
- 5/100
- issue の種類
- ドキュメント
- 明瞭さ
- 説明が足りない
- 活発さ
- 停滞
- 領域
- security
調査の方向性
This is a Microsoft security advisory posted as an issue, not a code task, and the payload names no files, tests or entry points. The affected-versions table gives the fixed PowerShell 7 releases (7.3.12 and 7.4.2), and the issue text does not say what change is wanted. Nothing here can be closed by a repository edit, so a newcomer should not start on it.
索引モデルが issue の本文から書いたものです。
説明
Microsoft Security Advisory CVE-2024-26190 | Microsoft QUIC Denial of Service Vulnerability
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in PowerShell 7.3 and PowerShell 7.4. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A Vulnerability exist in MsQuic.dll which might result in a peer to allocate small chunks of memory as long as connection stays alive. This issue only affects Windows systems.
System administrators are advised to update PowerShell 7 to an unaffected version (see affected software).
Discussion
Please open a support question to discuss the PowerShell aspects of this advisory.
Please use https://github.com/dotnet/runtime/issues/99620 for discussion of the .NET aspects this advisory.
Affected Software
The vulnerability affects PowerShell 7 prior to the following versions:
| PowerShell 7 Version | Fixed in |
|---|---|
| 7.3 | 7.3.12 |
| 7.4 | 7.4.2 |
The vulnerability affects PowerShell when running on the following operating systems:
| Operating System | Affected |
|---|---|
| Windows | Yes |
| macOS | Yes |
| Linux | Yes |
Advisory FAQ
How do I know if I am affected?
If all of the following are true:
- Run
pwsh -v, then, check the version in the table in Affected Software to see if your version of PowerShell 7 is affected.
How do I update to an unaffected version?
Follow the instructions at Installing PowerShell 7 to install the latest version of PowerShell 7.
Updating PowerShell 7 using Microsoft Update
Updating PowerShell 7 using Microsoft Update
Other Information
Reporting Security Issues
If you have found a potential security issue in PowerShell 7,
please email details to [email protected].
Support
You can ask questions about this issue on GitHub in the PowerShell organization.
This is located at https://github.com/PowerShell/.
The Announcements repo (https://github.com/PowerShell/Announcements)
will contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
What if the update breaks my script or module?
You can uninstall the newer version of PowerShell 7 and install the previous version of PowerShell 7.
This should be treated as a temporary measure.
Therefore, the script or module should be updated to work with the patched version of PowerShell 7.
Acknowledgments
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See acknowledgments for more information.
External Links
Revisions
V1.0 (April 09, 2024): Advisory published.
Version 1.0
Last Updated 2024-04-09
- 主要言語
- 言語のデータがありません
- スター
- 20
- フォーク
- 8
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
PowerShell/Announcements のほかの issue
-
PowerShell Security
難易度 5/5 1週間以上 初心者へのやさしさ 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
難易度 5/5 1週間以上 初心者へのやさしさ 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
難易度 2/5 1時間未満 初心者へのやさしさ 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
難易度 3/5 半日 初心者へのやさしさ 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
難易度 2/5 1時間未満 初心者へのやさしさ 8/100
PowerShell/Announcements#97 ·
PowerShell/Announcements の issue をすべて見る
似ている issue
-
from-review-extraction library privacy python severity:suggested
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
LearningCircuit/local-deep-research#7951 ·
メンテナーはふだん 2 日以内に返信
-
agent/reviewer
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
projectbluefin/utah-packages#634 ·
メンテナーはふだん 1 日以内に返信
-
io
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 73/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信