Microsoft Security Advisory CVE-2024-38095 | .NET Denial of Service Vulnerability
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 4/5
- Tempo estimado
- Mais de uma semana
- Facilidade para iniciantes
- 5/100
Direção de pesquisa
This is a published Microsoft security advisory for CVE-2024-38095, not a request for a code change, and the payload names no file, test or entry point in this repository. The only concrete step it gives is to run pwsh -v and compare the version with the fixed releases (7.2.22, 7.4.4). The technical discussion lives in the linked dotnet/runtime issue. A first-time contributor should not pick this up; the advisory has been stale for over two years.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Microsoft Security Advisory CVE-2024-38095 | .NET Denial of Service Vulnerability
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in PowerShell 7.2 and PowerShell 7.4. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A Vulnerability exists when System.Formats.Asn1 in .NET parses an X.509 certificate or collection of certificates, a malicious certificate can result in excessive CPU consumption on all platforms result in Denial of Service.
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/104622 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.2 | 7.2.22 |
| 7.4 | 7.4.4 |
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 (July 23, 2024): Advisory published.
Version 1.0
Last Updated 2024-07-23
- Linguagem predominante
- Sem dados de linguagem
- Estrelas
- 20
- Forks
- 8
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de PowerShell/Announcements
-
PowerShell Security
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
Dificuldade 3/5 Meio dia Facilidade para iniciantes 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 8/100
PowerShell/Announcements#97 ·
Todas as issues de PowerShell/Announcements
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 79/100
project-codeflare/codeflare-sdk#1195 ·
Mantenedores costumam responder em até 1 dia
-
account: profile bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 5 dias
-
kind/bug/report meta/needs triage
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
docker-mailserver/docker-mailserver#4831 ·
Mantenedores costumam responder em até 1 dia
-
ai-driven-fuzzing bug claude Minor
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 77/100
linagora/cozy-client#1766 ·
Mantenedores costumam responder em até 1 dia
-
enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
owasp-dep-scan/dep-scan#552 ·
Mantenedores costumam responder em até 1 dia