Bug 456378 - RHEL5: audit log injection attack via login
RHEL5: audit log injection attack via login
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: util-linux (Show other bugs)
All Linux
low Severity low
: rc
: ---
Assigned To: Karel Zak
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2008-07-23 04:39 EDT by Karel Zak
Modified: 2009-01-20 15:45 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 15:45:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:0070 normal SHIPPED_LIVE util-linux bug-fix update 2009-01-20 11:04:08 EST

  None (edit)
Description Karel Zak 2008-07-23 04:39:46 EDT
Steve Grubb wrote:
> A while back I found a couple audit log injection attacks which became
> CVE-2007-3102. I forgot to look at login to see if its vulnerable and Mirek
> found that it is. To verify the problem, type:
> root addr=xyz.com
> for the account name while logging in. It will look like root logged in with
> an address of xyz.com.

Note, the problem has been fixed in Fedora and upstream code.
Comment 1 RHEL Product and Program Management 2008-07-23 05:00:52 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
Comment 6 errata-xmlrpc 2009-01-20 15:45:35 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.