PHP PEAR 'Archive_Tar' Multiple Security Vulnerabilities



Date Discovered

December 18, 2019


PEAR Archive_Tar is prone to multiple security vulnerabilities. An attacker can exploit these issues to execute arbitrary code in the context of the application, obtain sensitive information, bypass certain security restrictions and perform unauthorized actions. PEAR Archive_Tar versions prior to 1.4.9 are vulnerable.

Technologies Affected

  • Drupal Drupal 7.0
  • Drupal Drupal 7.1
  • Drupal Drupal 7.10
  • Drupal Drupal 7.11
  • Drupal Drupal 7.12
  • Drupal Drupal 7.13
  • Drupal Drupal 7.14
  • Drupal Drupal 7.15
  • Drupal Drupal 7.16
  • Drupal Drupal 7.17
  • Drupal Drupal 7.18
  • Drupal Drupal 7.19
  • Drupal Drupal 7.2
  • Drupal Drupal 7.20
  • Drupal Drupal 7.21
  • Drupal Drupal 7.22
  • Drupal Drupal 7.23
  • Drupal Drupal 7.24
  • Drupal Drupal 7.25
  • Drupal Drupal 7.26
  • Drupal Drupal 7.27
  • Drupal Drupal 7.28
  • Drupal Drupal 7.29
  • Drupal Drupal 7.3
  • Drupal Drupal 7.30
  • Drupal Drupal 7.31
  • Drupal Drupal 7.32
  • Drupal Drupal 7.33
  • Drupal Drupal 7.34
  • Drupal Drupal 7.35
  • Drupal Drupal 7.36
  • Drupal Drupal 7.37
  • Drupal Drupal 7.38
  • Drupal Drupal 7.39
  • Drupal Drupal 7.4
  • Drupal Drupal 7.40
  • Drupal Drupal 7.41
  • Drupal Drupal 7.42
  • Drupal Drupal 7.43
  • Drupal Drupal 7.44
  • Drupal Drupal 7.5
  • Drupal Drupal 7.52
  • Drupal Drupal 7.54
  • Drupal Drupal 7.55
  • Drupal Drupal 7.56
  • Drupal Drupal 7.57
  • Drupal Drupal 7.58
  • Drupal Drupal 7.59
  • Drupal Drupal 7.6
  • Drupal Drupal 7.62
  • Drupal Drupal 7.65
  • Drupal Drupal 7.66
  • Drupal Drupal 7.67
  • Drupal Drupal 7.68
  • Drupal Drupal 7.8
  • Drupal Drupal 7.9
  • Drupal Drupal 8.7.0
  • Drupal Drupal 8.7.1
  • Drupal Drupal 8.7.10
  • Drupal Drupal 8.7.4
  • Drupal Drupal 8.7.5
  • Drupal Drupal 8.7.8
  • Drupal Drupal 8.7.9
  • Drupal Drupal 8.8.0
  • PEAR Archive_Tar 1.4.1
  • PEAR Archive_Tar 1.4.2
  • PEAR Archive_Tar 1.4.3
  • PEAR Archive_Tar 1.4.4
  • PEAR Archive_Tar 1.4.5
  • PEAR Archive_Tar 1.4.7
  • PEAR Archive_Tar 1.4.8


Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.

Run all software as a nonprivileged user with minimal access rights.
Attackers may successfully exploit client flaws in the browser through cross-site scripting vulnerabilities. When possible, run all software as a user with minimal privileges and limited access to system resources. Use additional precautions such as restrictive environments to insulate software that may potentially handle malicious content.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review its logs regularly.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Set web browser security to disable the execution of script code or active content.
Since a successful exploit of this issue allows malicious code to execute in web clients, consider disabling support for script code and active content within the client browser. Note that this mitigation tactic might adversely affect legitimate websites that rely on the execution of browser-based script code.

Updates are available. Please see the references or vendor advisory for more information.



Jasper Mattsson

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.