ghsa-3q76-jq6m-573p
Vulnerability from github
PEAR Archive_Tar version 1.4.3 and earlier contains a CWE-502, CWE-915 vulnerability in the Archive_Tar class. There are several file operations with $v_header['filename']
as parameter (such as file_exists, is_file, is_dir, etc). When extract is called without a specific prefix path, we can trigger unserialization by crafting a tar file with phar://[path_to_malicious_phar_file]
as path. Object injection can be used to trigger destruct in the loaded PHP classes, e.g. the Archive_Tar class itself. With Archive_Tar object injection, arbitrary file deletion can occur because @unlink($this->_temp_tarname)
is called. If another class with useful gadget is loaded, it may possible to cause remote code execution that can result in files being deleted or possibly modified. This vulnerability appears to have been fixed in 1.4.4.
{ "affected": [ { "package": { "ecosystem": "Packagist", "name": "pear/archive_tar" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "1.4.4" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2018-1000888" ], "database_specific": { "cwe_ids": [], "github_reviewed": true, "github_reviewed_at": "2023-07-07T13:42:43Z", "nvd_published_at": null, "severity": "HIGH" }, "details": "PEAR Archive_Tar version 1.4.3 and earlier contains a CWE-502, CWE-915 vulnerability in the Archive_Tar class. There are several file operations with `$v_header[\u0027filename\u0027]` as parameter (such as file_exists, is_file, is_dir, etc). When extract is called without a specific prefix path, we can trigger unserialization by crafting a tar file with `phar://[path_to_malicious_phar_file]` as path. Object injection can be used to trigger destruct in the loaded PHP classes, e.g. the Archive_Tar class itself. With Archive_Tar object injection, arbitrary file deletion can occur because `@unlink($this-\u003e_temp_tarname)` is called. If another class with useful gadget is loaded, it may possible to cause remote code execution that can result in files being deleted or possibly modified. This vulnerability appears to have been fixed in 1.4.4.", "id": "GHSA-3q76-jq6m-573p", "modified": "2023-07-07T13:42:43Z", "published": "2023-07-07T13:42:43Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2018-1000888" }, { "type": "WEB", "url": "https://github.com/pear/Archive_Tar/commit/59ace120ac5ceb5f0d36e40e48e1884de1badf76" }, { "type": "WEB", "url": "https://github.com/FriendsOfPHP/security-advisories/blob/master/pear/archive_tar/CVE-2018-1000888.yaml" }, { "type": "PACKAGE", "url": "https://github.com/pear/Archive_Tar" }, { "type": "WEB", "url": "https://lists.debian.org/debian-lts-announce/2019/02/msg00020.html" }, { "type": "WEB", "url": "https://pear.php.net/bugs/bug.php?id=23782" }, { "type": "WEB", "url": "https://security.gentoo.org/glsa/202006-14" }, { "type": "WEB", "url": "https://usn.ubuntu.com/3857-1" }, { "type": "WEB", "url": "https://web.archive.org/web/20210328115328/https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It\u0027s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdf" }, { "type": "WEB", "url": "https://web.archive.org/web/20220524160841/https://blog.sonarsource.com/new-php-exploitation-technique?redirect=rips" }, { "type": "WEB", "url": "https://www.debian.org/security/2019/dsa-4378" }, { "type": "WEB", "url": "https://www.exploit-db.com/exploits/46108" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "type": "CVSS_V3" } ], "summary": "Archive_Tar contains Potential RCE if filename starts with phar://" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.