Security readout for executives and security teams
Plain-English summary
This is a PHP library weakness in PEAR Archive_Tar 1.4.3 and earlier. If an application extracts attacker-supplied tar files in the affected way, a crafted archive can trigger unsafe PHP object handling, potentially causing file deletion and, with suitable loaded classes, possible remote code execution.
Executive priority
Treat as high priority where PHP systems process uploaded or external tar archives. The business concern is not broad internet exposure by default, but vulnerable archive handling can cross into destructive file operations or possible code execution. Patch and inventory affected PHP environments promptly.
Technical view
Archive_Tar uses archive header filenames in filesystem operations. The CVE states that crafted phar-style paths can trigger unserialization during extraction without a prefix path. Object injection may invoke destructors; Archive_Tar itself can lead to arbitrary file deletion, while other available gadget classes may expand impact.
Likely exposure
Exposure is most likely in PHP applications or servers using PEAR Archive_Tar 1.4.3 or earlier, including distribution packages referenced by Debian, Ubuntu, and Gentoo advisories. Practical risk depends on whether untrusted archives are extracted and whether vulnerable extraction conditions are reachable.
Exploitation context
The bundle includes an Exploit-DB reference, so public exploit information exists. It does not show CISA KEV listing or confirmed active exploitation. Impact is context-dependent because remote code execution requires useful loaded gadget classes, while file deletion is specifically described for Archive_Tar object injection.
Researcher notes
The source record names CWE-502 and CWE-915 patterns, but the supplied CVE metadata lacks CVSS details. Scope validation should focus on vulnerable versions, untrusted archive extraction, prefix-path behavior, and available PHP classes that could influence deserialization impact.
Mitigation direction
- Upgrade PEAR Archive_Tar to 1.4.4 or a vendor-fixed package.
- Apply Debian, Ubuntu, or Gentoo security updates where those packages are used.
- Avoid extracting untrusted tar archives with affected Archive_Tar versions.
- Check vendor guidance before relying on custom mitigations.
- Restrict archive processing to trusted workflows until fixed.
Validation and detection
- Inventory PEAR Archive_Tar versions in PHP applications and system packages.
- Identify code paths that extract user-supplied or remote tar archives.
- Confirm whether extraction occurs without a specific prefix path.
- Review package manager status against Debian, Ubuntu, or Gentoo advisories.
- Check file integrity around systems that processed untrusted archives.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-1000888 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- [debian-lts-announce] 20190212 [SECURITY] [DLA 1674-1] php5 security updateCVE reference · mailing-list, x_refsource_MLIST
- USN-3857-1CVE reference · vendor-advisory, x_refsource_UBUNTU
- DSA-4378CVE reference · vendor-advisory, x_refsource_DEBIAN
- 46108CVE reference · exploit, x_refsource_EXPLOIT-DB
- https://pear.php.net/package/Archive_Tar/download/CVE reference · x_refsource_CONFIRM
- https://cdn2.hubspot.net/hubfs/3853213/us-18-Thomas-It%27s-A-PHP-Unserialization-Vulnerability-Jim-But-Not-As-We-....pdfCVE reference · x_refsource_MISC
- https://blog.ripstech.com/2018/new-php-exploitation-technique/CVE reference · x_refsource_MISC
- https://pear.php.net/bugs/bug.php?id=23782CVE reference · x_refsource_CONFIRM
- GLSA-202006-14CVE reference · vendor-advisory, x_refsource_GENTOO
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.