Microsoft Security Advisory: PowerShell Defense in Depth Updates
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 1/5
- Temps estimé
- Moins d'une heure
- Accessibilité débutants
- 5/100
Piste de recherche
This is a published Microsoft security advisory with no requested code change, and the payload names no files, tests or entry points. The affected-versions table and the FAQ are the only content, and the issue has no comments or linked pull request. Questions about the PowerShell aspects belong in a support question on the PowerShell/PowerShell repository, as the advisory itself says.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Microsoft Security Advisory: PowerShell Defense in Depth Updates
Executive Summary
An issue exists in PowerShell that could lead to unauthorized command access that is being addressed by defense-in-depth measures in PowerShell 7.
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.
Mitigation factors
The following mitigating factors might be helpful in your situation. This issue does not affect you:
- If you deploy App Control for Business with script in enforcement mode.
- If you do not deploy AppLocker script rules in enforcement mode.
Affected Software
The vulnerability affects PowerShell 7 prior to the following versions:
| PowerShell 7 Version | Affected version | Patched Version |
|---|---|---|
| 7.5 | <7.5.1 | 7.5.1 |
| 7.4 | <7.4.10 | 7.4.10 |
The vulnerability affects PowerShell when running on the following operating systems:
| Operating System | Affected |
|---|---|
| Windows | Yes |
| macOS | No |
| Linux | No |
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
- Aaron Margosis
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See acknowledgments for more information.
Revisions
V1.1 (May 15, 2025): Added acknowledgment.
V1.0 (May 15, 2025): Advisory published.
Version 1.1
Last Updated 2023-05-15
- Langage dominant
- Aucune donnée de langage
- Étoiles
- 20
- Forks
- 8
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de PowerShell/Announcements
-
PowerShell Security
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
Difficulté 5/5 Plus d'une semaine Accessibilité débutants 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
Difficulté 2/5 Moins d'une heure Accessibilité débutants 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
Difficulté 3/5 Une demi-journée Accessibilité débutants 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
Difficulté 2/5 Moins d'une heure Accessibilité débutants 8/100
PowerShell/Announcements#97 ·
Toutes les issues de PowerShell/Announcements
Issues similaires
-
external-issue to-triage
Difficulté 2/5 1-3 heures Accessibilité débutants 71/100
Les mainteneurs répondent en général sous 1 jour
-
feature
Difficulté 2/5 1-3 heures Accessibilité débutants 64/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
btclib-org/btclib-wallet#733 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 67/100
arkavo-org/ArkavoKit#70 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
crowdsecurity/hub#1999 ·
Les mainteneurs répondent en général sous 1 jour