RHSA-2010:0141: Moderate: tar security update
First published: Mon Mar 15 2010(Updated: )
The GNU tar program saves many files together in one archive and can<br>restore individual files (or all of the files) from that archive.<br>A heap-based buffer overflow flaw was found in the way tar expanded archive<br>files. If a user were tricked into expanding a specially-crafted archive,<br>it could cause the tar executable to crash or execute arbitrary code with<br>the privileges of the user running tar. (CVE-2010-0624)<br>Red Hat would like to thank Jakob Lell for responsibly reporting the<br>CVE-2010-0624 issue.<br>A denial of service flaw was found in the way tar expanded archive files.<br>If a user expanded a specially-crafted archive, it could cause the tar<br>executable to crash. (CVE-2007-4476)<br>Users of tar are advised to upgrade to this updated package, which contains<br>backported patches to correct these issues.
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/tar | <1.15.1-23.0.1.el5_4.2 | 1.15.1-23.0.1.el5_4.2 |
| redhat/tar | <1.15.1-23.0.1.el5_4.2 | 1.15.1-23.0.1.el5_4.2 |
| redhat/tar | <1.14-13.el4_8.1 | 1.14-13.el4_8.1 |
| redhat/tar | <1.14-13.el4_8.1 | 1.14-13.el4_8.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of RHSA-2010:0141?
The severity of RHSA-2010:0141 is classified as moderate.
How do I fix RHSA-2010:0141?
To fix RHSA-2010:0141, update the tar package to version 1.15.1-23.0.1.el5_4.2 or 1.14-13.el4_8.1, depending on your system.
Which systems are affected by RHSA-2010:0141?
RHSA-2010:0141 affects systems running tar versions 1.14 and 1.15.1 prior to specified updates.
What type of vulnerability is identified in RHSA-2010:0141?
RHSA-2010:0141 identifies a heap-based buffer overflow flaw in the GNU tar program.
Is there a workaround for RHSA-2010:0141 if I can't update immediately?
While the only effective solution is to update the tar package, avoiding the use of tar for handling untrusted archives may serve as a temporary workaround.
- agent/references
- agent/severity
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/last-modified-date
- agent/weakness
- agent/remedy
- agent/title
- agent/description
- collector/redhat-errata
- source/Red Hat
- anchor-id/RHSA-2010:0141
- agent/software-canonical-lookup
- agent/event
- agent/trending
- agent/tags
- agent/source
- package-manager/redhat