Authenticated file modification via permissive installation ACLs
Published Nov 29, 2022 · Updated Apr 25, 2025
Incorrect permissions in Chocolatey Python3 3.11.0 and earlier allow remote authenticated users to modify installed Python files. The package assigns the Authenticated Users group write access to C:\Python311 and every file beneath that installation directory. Exploitation requires an authenticated Windows account with filesystem reachability; the documented consequence is unauthorized file modification.
Summary
What happened
Incorrect permissions in Chocolatey Python3 3.11.0 and earlier allow remote authenticated users to modify installed Python files. The package assigns the Authenticated Users group write access to C:\Python311 and every file beneath that installation directory. Exploitation requires an authenticated Windows account with filesystem reachability; the documented consequence is unauthorized file modification.
The record
- CVE
- CVE-2022-45305
- Published
- Nov 29, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 29, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo