CVE-2025-33055
published 2025-06-10CVE-2025-33055: Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.
PriorityP424medium5.5CVSS 3.1
AVLACLPRLUINSUCHINAN
EPSS
0.54%
41.8th percentile
Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.
Affected
41 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gnu | tar | >= 0 < 0.4.45 | 0.4.45 |
| gnu | tar | >= 0.0.0-0 < 0.4.45 | 0.4.45 |
| microsoft | windows_10_1507 | < 10.0.10240.21034 | 10.0.10240.21034 |
| microsoft | windows_10_1607 | < 10.0.14393.8148 | 10.0.14393.8148 |
| microsoft | windows_10_1809 | < 10.0.17763.7434 | 10.0.17763.7434 |
| microsoft | windows_10_21h2 | < 10.0.19044.5965 | 10.0.19044.5965 |
| microsoft | windows_10_22h2 | < 10.0.19045.5965 | 10.0.19045.5965 |
| microsoft | windows_10_version_1507 | >= 10.0.10240.0 < 10.0.10240.21034 | 10.0.10240.21034 |
| microsoft | windows_10_version_1607 | >= 10.0.14393.0 < 10.0.14393.8148 | 10.0.14393.8148 |
| microsoft | windows_10_version_1809 | >= 10.0.17763.0 < 10.0.17763.7434 | 10.0.17763.7434 |
| microsoft | windows_10_version_21h2 | >= 10.0.19044.0 < 10.0.19044.5965 | 10.0.19044.5965 |
| microsoft | windows_10_version_22h2 | >= 10.0.19045.0 < 10.0.19045.5965 | 10.0.19045.5965 |
| microsoft | windows_11_22h2 | < 10.0.22621.5472 | 10.0.22621.5472 |
| microsoft | windows_11_23h2 | < 10.0.22631.5472 | 10.0.22631.5472 |
| microsoft | windows_11_24h2 | < 10.0.26100.4270 | 10.0.26100.4270 |
| microsoft | windows_11_version_22h2 | >= 10.0.22621.0 < 10.0.22621.5472 | 10.0.22621.5472 |
| microsoft | windows_11_version_22h3 | >= 10.0.22631.0 < 10.0.22631.5472 | 10.0.22631.5472 |
| microsoft | windows_11_version_23h2 | >= 10.0.22631.0 < 10.0.22631.5472 | 10.0.22631.5472 |
| microsoft | windows_11_version_24h2 | >= 10.0.26100.0 < 10.0.26100.4349 | 10.0.26100.4349 |
| microsoft | windows_server_2016 | < 10.0.14393.8148 | 10.0.14393.8148 |
| microsoft | windows_server_2016 | >= 10.0.14393.0 < 10.0.14393.8148 | 10.0.14393.8148 |
| microsoft | windows_server_2019 | < 10.0.17763.7434 | 10.0.17763.7434 |
| microsoft | windows_server_2019 | >= 10.0.17763.0 < 10.0.17763.7434 | 10.0.17763.7434 |
| microsoft | windows_server_2022 | < 10.0.20348.3745 | 10.0.20348.3745 |
| microsoft | windows_server_2022 | >= 10.0.20348.0 < 10.0.20348.3807 | 10.0.20348.3807 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
ghsa8.1HIGH
osv8.1HIGH
vendor_msrc5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
tar-rs incorrectly ignores PAX size headers if header size is nonzero
ghsa·2026-03-20·CVSS 8.1
CVE-2026-33055 [HIGH] CWE-843 tar-rs incorrectly ignores PAX size headers if header size is nonzero
tar-rs incorrectly ignores PAX size headers if header size is nonzero
### Summary
As part of [CVE-2025-62518](https://www.cve.org/CVERecord?id=CVE-2025-62518) the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header.
However, it was missed at the time that this project (the original Rust `tar` crate) had a conditional logic that skipped the PAX size header in the case that the base header size was nonzero - almost the inverse of the astral-tokio-tar issue.
The problem here is that *any* discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers.
In this case, the tar-rs (Rust `tar`) crate is an outlier in checking for the header si
OSV
tar-rs incorrectly ignores PAX size headers if header size is nonzero
osv·2026-03-19·CVSS 8.1
CVE-2026-33055 tar-rs incorrectly ignores PAX size headers if header size is nonzero
tar-rs incorrectly ignores PAX size headers if header size is nonzero
Versions 0.4.44 and below of tar-rs have conditional logic that skips the PAX
size header in cases where the base header size is nonzero.
As part of [CVE-2025-62518][astral-cve], the [astral-tokio-tar]
project was changed to correctly honor PAX size headers in the case where it
was different from the base header. This is almost the inverse of the
astral-tokio-tar issue.
Any discrepancy in how tar parsers honor file size can be used to create
archives that appear differently when unpacked by different archivers. In this
case, the tar-rs (Rust tar) crate is an outlier in checking for the header size
— other tar parsers (including e.g. Go [`archive/tar`][go-tar]) unconditionally
use the PAX size override. This can affect
GHSA
GHSA-8pqc-m8ff-xf67: Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally
ghsa_unreviewed·2025-06-10
CVE-2025-33055 [MEDIUM] CWE-125 GHSA-8pqc-m8ff-xf67: Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally
Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.
Microsoft
Windows Storage Management Provider Information Disclosure Vulnerability
vendor_msrc·2025-06-10·CVSS 5.5
CVE-2025-33055 [MEDIUM] CWE-125 Windows Storage Management Provider Information Disclosure Vulnerability
Windows Storage Management Provider Information Disclosure Vulnerability
Description: Out-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information locally.
FAQ: What type of information could be disclosed by this vulnerability?
An attacker who successfully exploited this vulnerability could potentially read small portions of heap memory.
Windows Storage Management Provider: Windows Storage Management Provider
Microsoft: Microsoft
Customer Action Required: Yes
Impact: Information Disclosure
Exploit Status: Publicly Disclosed:No;Exploited:No;Latest Software Release:Exploitation Unlikely
Reference: https://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5060531
Reference: https://support.microsoft.com/help/5060531
Reference: ht
No detection rules found.
No public exploits indexed.
2025-06-10
Published