Updated minicom packages available
| Advisory: | RHSA-2001:067-03 |
|---|---|
| Type: | Security Advisory |
| Severity: | N/A |
| Issued on: | 2001-05-03 |
| Last updated on: | 2001-05-09 |
| Affected Products: | Red Hat Linux 6.2 Red Hat Linux 7.0 Red Hat Linux 7.1 |
| CVEs (cve.mitre.org): |
CVE-2001-0570 |
Details
The minicom program allows any user with local shell access to obtain
group uucp priveledges. It may also be possible for the malicious user
to obtain root priveledges as well.
Minicom contains a great number of format string abuses in it's usage
of several printf-like varargs functions. The program was never written
with security in mind, and as such even though many format strings bugs
have been fixed in this release, there are many more lurking in the code.
This release solves the security problem by disabling setgid uucp on the
minicom binary.
Solution
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains the
desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains the
desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
Updated packages
| Red Hat Linux 6.2 | |
| SRPMS: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-1.0.6x/SRPMS/minicom-1.83.1-1.0.6x.src.rpm Missing file |
MD5: d6ecd41e7df093ca62f8d1ab15a2d51c |
| Alpha: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-1.0.6x/alpha/minicom-1.83.1-1.0.6x.alpha.rpm Missing file |
MD5: b27358ca1604b2ca5fa8ec6a34fa6349 |
| IA-32: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-1.0.6x/i386/minicom-1.83.1-1.0.6x.i386.rpm Missing file |
MD5: 158495648d2d3f8a2636d345249fc01a |
| Sparc: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-1.0.6x/sparc/minicom-1.83.1-1.0.6x.sparc.rpm Missing file |
MD5: ca9069a87bfa81fe730cb8f31378e57a |
| Red Hat Linux 7.0 | |
| SRPMS: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-8/SRPMS/minicom-1.83.1-8.src.rpm Missing file |
MD5: 599a686fa0598467f5ee451f934c8a28 |
| Alpha: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-8/alpha/minicom-1.83.1-8.alpha.rpm Missing file |
MD5: 2da88e6d8479ccb35078ec1a469b3568 |
| IA-32: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-8/i386/minicom-1.83.1-8.i386.rpm Missing file |
MD5: 5cfe67255b3ec7df6c3f1b274da3c7ad |
| Red Hat Linux 7.1 | |
| SRPMS: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-8/SRPMS/minicom-1.83.1-8.src.rpm Missing file |
MD5: 599a686fa0598467f5ee451f934c8a28 |
| IA-32: | |
| ftp://updates.redhat.com/rhn/repository/NULL/minicom/1.83.1-8/i386/minicom-1.83.1-8.i386.rpm Missing file |
MD5: 5cfe67255b3ec7df6c3f1b274da3c7ad |
References
Keywords
exploit
These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package
The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/