async-tar
Activity
- Latest release
- 3mo ago
- Total releases
- 12
- Cadence
- ~3 months
- Last 12 months
- 3
Details
- License
- MIT/Apache-2.0
- First release
- Dec 24, 2019
| Version | Released | |
|---|---|---|
0.6.1
unknown
|
0.6.1
unknown
Dependencies (12)
+ 4 more |
|
0.6.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (12)
+ 4 more |
|
0.5.1
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.1
unknown
Dependencies (9)
+ 1 more |
|
0.5.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (9)
+ 1 more |
|
0.4.2
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.2
unknown
Dependencies (9)
+ 1 more |
|
0.4.1
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.1
unknown
Dependencies (9)
+ 1 more |
|
0.4.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.4.0
unknown
Dependencies (9)
+ 1 more |
|
0.3.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (9)
+ 1 more |
|
0.2.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.2.0
unknown
Dependencies (9)
+ 1 more |
|
0.1.2
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.1.2
unknown
Dependencies (8)
|
|
0.1.1
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.1.1
unknown
Dependencies (8)
|
|
0.1.0
unknown
1 CVE
CVE-2026-53600
GHSA-35rm-7j9c-2f7m
Jul 08, 2026
async-tar PAX extension-header desync enables tar entry/content smuggling
Medium
Network
Low
None
None
Summary
An attacker who can influence a tar stream that an Type confusion / improper validation of the specified quantity (size). CWE-20, CWE-843. Severity assessed Medium, consistent with the same defect class in the upstream tar-rs / tokio-tar lineage. Affected codePackage:
and a few lines further down the same function:
The caller loop in The buffered PAX records are intended to apply only to the following file
entry; the missing check is whether the raw header currently being sized is itself
an extension header ( ImpactDifferential extraction / entry smuggling. A consumer that extracts an
attacker-influenced tar stream with
This breaks any security control that relies on scanning the archive with one
parser and extracting with How input reaches the sink (reachability)The vulnerable path is the library's primary public API for reading archives:
Proof of conceptA standalone Rust consumer binary that links the published crates.io
Malicious archive geometry (block = 512 bytes):
GNU tar honours the Tar-builder source (
Consumer source (
End-to-end reproductionReference parser: GNU tar 1.35. async-tar: the v0.6.0 crates.io release linked by the consumer binary above. Verbatim captured output:
Same bytes, two parsers, different on-disk result: GNU tar writes a 1024-byte
benign blob; Negative control — a benign archive (correct PAX usage:
GNU tar and FixApply the buffered PAX records (and the
Fix-verify, captured verbatim. The patched
With the guard, Fix PRA fix PR adding the CreditReported by tonghuaroot. Fixed in
0.6.1
References Updated Sep 10, 2026 · Source: OSV.dev |
0.1.0
unknown
Dependencies (8)
|