Microsoft Security Advisory CVE-2023-33127: .NET Remote Code Execution Vulnerability
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 1/5
- Tempo stimato
- Meno di un'ora
- Idoneità per principianti
- 5/100
Direzione di ricerca
This is a published Microsoft advisory for CVE-2023-33127, not a change request, and the body names no file, test or entry point to edit. The affected-versions table (PowerShell 7.2 before 7.2.13, 7.3 before 7.3.6, Windows only) is the only concrete content. Discussion is directed to dotnet/runtime#88674 and PowerShell support questions, so there is no defined 'done' for a newcomer.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Microsoft Security Advisory CVE-2023-33127: .NET Remote Code Execution Vulnerability
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in the version of .NET used in PowerShell 7.2 and 7.3. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A vulnerability exists in .NET applications where the diagnostic server can be exploited to achieve cross-session/cross-user elevation of privilege (EoP) and code execution.
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 dotnet/runtime#88674 for discussion of the .NET runtime aspects this advisory.
Affected Software
The vulnerability affects PowerShell 7 prior to the following versions:
| PowerShell 7 Version | Fixed in |
|---|---|
| 7.2 | 7.2.13 |
| 7.3 | 7.3.6 |
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
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 13, 2023): Advisory published.
Version 1.0
Last Updated 2023-07-13
- Lingua principale
- Nessun dato sulla lingua
- Stelle
- 20
- Fork
- 8
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di PowerShell/Announcements
-
PowerShell Security
Difficoltà 5/5 Più di una settimana Idoneità per principianti 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
Difficoltà 5/5 Più di una settimana Idoneità per principianti 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
Difficoltà 2/5 Meno di un'ora Idoneità per principianti 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
Difficoltà 3/5 Mezza giornata Idoneità per principianti 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
Difficoltà 2/5 Meno di un'ora Idoneità per principianti 8/100
PowerShell/Announcements#97 ·
Tutte le issue di PowerShell/Announcements
Issue simili
-
Mend: dependency security vulnerability
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
kube-tarian/sigrun#203 ·
-
Area: Infrastructure Chore Difficulty: Low Priority: Medium
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
DouglasNeuroInformatics/OpenDataCapture#1835 ·
I maintainer di solito rispondono entro 1 giorno
-
ai_context (Express): `express.raw()` / `bodyParser.raw()` body parser reported as an XSS sinkAperta🐞 bug 🧩 ai-context
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
owasp-noir/noir#3295 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
Agent-Field/CodeAF#2022 ·
I maintainer di solito rispondono entro 1 giorno
-
auth-rbac enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100
I maintainer di solito rispondono entro 1 giorno