Goal Reached Thanks to every supporter โ€” we hit 100%!

Goal: 1000 CNY ยท Raised: 1336 CNY

100%

CVE-2020-36193 โ€” AI Deep Analysis Summary

Q1What is this vulnerability? (Essence + Consequences)

๐Ÿšจ **Essence**: A **Post-Link Vulnerability** in Pear Archive_Tar. ๐Ÿ“ฆ It allows **Directory Traversal** attacks.โ€ฆ

Q2Root Cause? (CWE/Flaw)

๐Ÿ›ก๏ธ **Root Cause**: The flaw lies in how **Archive_Tar** handles tar archives. It fails to properly validate paths during extraction, allowing **Malicious Symlinks** or paths to escape the target directory.โ€ฆ

Q3Who is affected? (Versions/Components)

๐Ÿ‘ฅ **Affected**: **Pear Archive_Tar** library. ๐Ÿ“‰ Specifically versions **through 1.4.11**. ๐Ÿ‡บ๐Ÿ‡ธ Widely used in **Drupal** and **Fedora**/Debian Linux environments. ๐Ÿ˜ If you use PHP PEAR for tar handling, you are at risk.

Q4What can hackers do? (Privileges/Data)

๐Ÿ•ต๏ธ **Hacker Capabilities**: Can write files to **Arbitrary Directories**. ๐Ÿ“ This leads to **Remote Code Execution (RCE)** if they overwrite config files or scripts.โ€ฆ

Q5Is exploitation threshold high? (Auth/Config)

๐Ÿ”“ **Exploitation Threshold**: **Medium**. ๐Ÿ“Š Requires the application to process **Untrusted Tar Archives**. ๐Ÿ“ค No authentication needed for the archive upload itself, but the app must extract it.โ€ฆ

Q6Is there a public Exp? (PoC/Wild Exploitation)

๐Ÿงช **Public Exploit**: **Yes**. ๐ŸŒ References confirm active exploitation in the wild (e.g., **Drupal SA-CORE-2021-001**). ๐Ÿ“ข Multiple vendor advisories (Fedora, Debian) indicate widespread public awareness and PoCs exist.โ€ฆ

Q7How to self-check? (Features/Scanning)

๐Ÿ” **Self-Check**: Scan for **Pear Archive_Tar** usage in PHP projects. ๐Ÿ˜ Check version numbers: if **<= 1.4.11**, you are vulnerable. ๐Ÿ“‹ Look for tar extraction functions in your codebase.โ€ฆ

Q8Is it fixed officially? (Patch/Mitigation)

โœ… **Official Fix**: **Yes**. ๐Ÿ› ๏ธ Patches released by vendors. ๐Ÿ“… Fedora and Debian have issued security updates. ๐Ÿ”„ Upgrade to **Archive_Tar > 1.4.11** or apply vendor-specific patches (e.g., Drupal core updates). ๐Ÿ“ฆ

Q9What if no patch? (Workaround)

๐Ÿšง **No Patch Workaround**: **Disable** tar extraction features if not needed. ๐Ÿšซ Validate all uploaded files strictly before processing. ๐Ÿ›ก๏ธ Use **Chroot** or **Sandboxing** to limit file system access.โ€ฆ

Q10Is it urgent? (Priority Suggestion)

๐Ÿšจ **Urgency**: **CRITICAL**. ๐Ÿ”ด High impact (RCE/Write Access). ๐ŸŒ Widely exploited in major platforms like Drupal. ๐Ÿ“‰ Immediate patching or mitigation required. โณ Do not delay! Update libraries or apply vendor fixes ASAP.โ€ฆ